trillium VS routerify

i like trillium a lot. inspired by plug (elixir), you just add plugs in a vertical stack and the request goes from top to bottom. there is also ntex which has a ton of examples inspired by actix-web (might have been a fork) https://github.com/ntex-rs/examples

Maybe you want something like this, which is a Cow-like enum that either holds a &mut T or a T?

I've been planning on using trillium on a project, the main difference I can see between it and Axum is that Axum allows you to use existing tower middle ware, right?

I'll definitely prioritize this! I hadn't really thought much about it because it's straightforward to do in application code, but it seems reasonable to make it easier for people to get started with this common use case. I opened up a discussion on gh, let me know if something like what you had in mind https://github.com/trillium-rs/trillium/discussions/36

Any thoughts on (trillium)[https://github.com/trillium-rs/trillium]? Looks like you're fulfilling similar niches.

You can checkout an example AWS Lambda entrypoint for an HTTP library Routerify (very similar to Axum) here: https://github.com/routerify/routerify/blob/master/examples/aws_lambda.rs

https://github.com/routerify/routerify is an easy to use router built on Hyper.

Looks interesting. How does this compare to routerify?

I'd also recommend routerify. It is a small layer on top of hyper but it makes writing HTTP servers quite enjoyable. My colleague dhruvasagar is creating a series of screencasts for building a URL shortener with Rust. Do check his series.

Routerify-lite is a simplified but faster version of Routerify.

I haven't deployed Rust on lambda yet. However, I was meaning to experiment with routerify in the coming weeks. It has an example for AWS lambda as well. Let me know how it works out.