i don't think poem is too bad (esp. considering openapi stuff), it's mostly just that axum and dropshot have entire teams allocated to them whereas poem and some of the other frameworks are basically a bus factor of 1
What do you like about poem compared to axum/dropshot? I've never used it (previously used all of actixweb, axum and dropshot for various prod services at work)
i wish i was qualified to answer this question!
at the time i initiated the company stack rewrite to Rust, i knew a lot less about the language, & we adopted poem_openapi basically because the most senior Rust dev at the company had used it for his previous startup's server & we could ship faster
Fair enough! I think the niche it fills is for people who really want OpenAPI support as a built-in, primary concern. But unlike Dropshot (which also offers that) they want middleware. Dropshot is very anti-middleware.
like right now we're shipping a new service and showing it to prospective clients, having that built in interactive docs for the server is killer. we can just send that to them with an api key
That's awesome. We built our own doc-generator that consumes the openapi.json output from Dropshot, but having more of that stuff built in would be great.
Comments
at the time i initiated the company stack rewrite to Rust, i knew a lot less about the language, & we adopted poem_openapi basically because the most senior Rust dev at the company had used it for his previous startup's server & we could ship faster
Been using Axum for while, but OpenAPI and anti middleware sounds interesting to me for sure