poem VS salvo

https://github.com/poem-web/poem is one Rust framework with swagger definitions out of the box.

There is one: Poem[1]

The author mentions flask but looking at the "What we need section", I don't think flask covers those. I hate Djago with a passion but if those are the requirements, I think Django is the one that closely resembles what the author is describing. So Poem is not a good candidate either in that regard. Poem is all in all, something that closely resembles FastAPI, which is actually a complement. I've tried half a dozen rust web frameworks and they all come with a ton of boilerplate fiddling with the initial setup. Which is a problem if you want to get things done fast. In that regard, poem nails it. Yes, actix has a considerably better performance but unless you are aiming for sub-30 millisecond responses, then actix is not what you should be looking at to begin with. Also if you crave a Pydantic, there is a crate that sort of does that for you: https://crates.io/crates/poem-openapi

[1] https://github.com/poem-web/poem

TypeSpec is great, but if you're working with Rust and you're about to write a new project that will require an OpenApi spec sooner or later, I'd like to recommend a web framework that has spec generation baked in:

https://github.com/poem-web/poem (see poem_openapi)

All you need to do is derive a trait on your response structs and in return you get an almost perfectly generated spec. Unions, objects, enums are first class citizens.

Also, if you're from coming from PHP, the controllers feel very much like symfony controllers.

P.s. Please do recommend an ORM that would feel closer to doctrine. I miss doctrine.

I've used FastAPI/Pydantic before as well and it was a very good experience. It has been a while since I used them though, so I forget exactly how they compare, but I do recall it wrote most of the OpenAPI spec. for you. I will also agree when I saw utoipa and aide they seemed to require more boilerplate even though I have not done an actual comparison. Poem, on the other hand, seems very neat and clean and doesn't have any duplication that I can see. Here is the [TODO example](https://github.com/poem-web/poem/blob/master/examples/openapi/todos/src/main.rs).

The example at https://github.com/poem-web/poem/tree/master/examples/openapi/auth-apikey works without issues for me.

'Poem', it turns to nicer to play with for me than 'Axum'. Example of web socket chat https://github.com/poem-web/poem/blob/master/examples/poem/websocket-chat/src/main.rs

If you need built-in OpenAPI support, I can recommend Poem.

If OpenAPI is important, then you may to consider https://github.com/poem-web/poem instead of axum. It isn't nearly as widely used, but it should still be compatible with everything else.

Poem: More rigid and less popular and aims to be easier https://github.com/poem-web/poem

Did you check out Poem? It seems promising, with openapi generation built in already.

Supports for hyper v1 (through a feature flag) and therefore it is compatible with the salvo library!

I have integrated it into my open-source web framework salvo. However, I would like to use a custom WebTransportSession. Many structs do not have public functions to create instances.

https://github.com/salvo-rs/salvo/blob/main/examples/oapi-generics/src/main.rshttps://github.com/salvo-rs/salvo/blob/main/examples/oapi-todos/src/main.rs

https://next.salvo.rs/ As simple as golang web framework

If you come from golang or nodejs. You can try salvo: https://github.com/salvo-rs/salvo

Salvo's main branch is base on hyper 1.0-rc.3 now. Welcome to test and give feedback. https://github.com/salvo-rs/salvo

Salvo (https://salvo.rs/)

Maybe not with Actix, but certainly with axum: https://github.com/tokio-rs/axum

Salvo is also great: https://salvo.rs

If one were to undertake a project of developing something like this, which is the best web framework for it. I did some cursory research and discovered these back-end frameworks - actix, axum, poem, salvo, warp, gotham and rocket.

Salvo update hyper dependency to v1.0.0-rc.1 now in next branch, and Http3 added! https://github.com/salvo-rs/salvo/tree/next