{"slug": "axum", "name": "Axum", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 2, "commenters": 6, "warners": 1, "score": 1.738, "rising": 2.0, "first": "2026-01-02", "latest": "2026-10-14", "why": "My Lambda's are monolith webapps using Axum Rust framework.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 2, "neutral": 2, "compare": 1, "warn": 1}, "spark": [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2], "listed": false, "loved": [], "caveat": "", "short_quote": "My Lambda's are monolith webapps using Axum Rust framework.", "icon": false, "domain": null, "github_repo": null, "official_url": "", "pricing": "", "aliases": ["Axum"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 801345264, "item_id": 50084079, "url": "https://news.ycombinator.com/item?id=50084079", "by": "tiew9Vii", "date": "2026-10-14", "stance": "recommend", "quote": "My Lambda's are monolith webapps using Axum Rust framework.", "excerpt": "> Are we pretending now it's less complicated to distribute an app a cross a variety of lambda functions? I treat Lambda purely as compute and ignore everything else related to \"serverless\". My Lambda's are monolith webapps using Axum Rust framework. Using cargo lambda I generate a static binary, upload to s3 and point the lambda at it. Sometimes I'll package as a docker image so can run in Lambda or locally by passi", "context": "", "use_case": "Lambda web apps", "switched_from": "", "story": "AWS Lambda Web Functions"}, {"id": 801234594, "item_id": 50077162, "url": "https://news.ycombinator.com/item?id=50077162", "by": "nemothekid", "date": "2026-10-13", "stance": "recommend", "quote": "Rust + Axum has sort of supported this with a middleware", "excerpt": "Rust + Axum has sort of supported this with a middleware (https://github.com/lazear/axum-aws-lambda). Essentially you write your API as normal, and then when you build for lambda you enable a feature that does the special handler for you. This + Function URL + Cloudfront, and you end up with an API entirely hosted in lambda. I have a backend that does is hosted like this that does pretty complex work (image/video upl", "context": "", "use_case": "web API framework", "switched_from": "", "story": "AWS Lambda Web Functions"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 798190225, "item_id": 49886889, "url": "https://news.ycombinator.com/item?id=49886889", "by": "dgroshev", "date": "2026-09-29", "stance": "warn", "quote": "Fragile boilerplate.", "excerpt": "Fragile boilerplate. I love \"Zero to Production in Rust\", but that's a pretty long book that recreates a fraction of what comes out of the box with Django. Also, when things come with Django, there's no need to maintain or worry about subtle yet crucial bugs.", "context": "", "use_case": "ecommerce/CRUD web apps", "switched_from": "", "story": "What About Rails?"}]}], "who": [{"by": "brainless", "context": "builds product backends in Rust", "url": "https://news.ycombinator.com/item?id=50065780", "date": "2026-10-13"}], "tags": [], "use_cases": ["lambda web apps", "web api framework", "rust web backends", "ecommerce/crud web apps", "ecommerce/crud apps", "web server framework"], "compared": [{"slug": "ruby-on-rails", "name": "Ruby on Rails", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "django", "name": "Django", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "aws-lambda", "name": "AWS Lambda", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "diesel", "name": "Diesel", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=50069318", "title": "AWS Lambda Web Functions", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49839664", "title": "What About Rails?", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50058528", "title": "A Modern Web App in C", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46466074", "title": "Ask HN: Who is hiring? (January 2026)", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"neutral": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {"compare": 1, "warn": 1}, "2026-10": {"neutral": 1, "recommend": 2}}, "quotes": [{"id": 801345264, "item_id": 50084079, "url": "https://news.ycombinator.com/item?id=50084079", "by": "tiew9Vii", "date": "2026-10-14", "stance": "recommend", "quote": "My Lambda's are monolith webapps using Axum Rust framework.", "excerpt": "> Are we pretending now it's less complicated to distribute an app a cross a variety of lambda functions? I treat Lambda purely as compute and ignore everything else related to \"serverless\". My Lambda's are monolith webapps using Axum Rust framework. Using cargo lambda I generate a static binary, upload to s3 and point the lambda at it. Sometimes I'll package as a docker image so can run in Lambda or locally by passi", "context": "", "use_case": "Lambda web apps", "switched_from": "", "story": "AWS Lambda Web Functions"}, {"id": 801234594, "item_id": 50077162, "url": "https://news.ycombinator.com/item?id=50077162", "by": "nemothekid", "date": "2026-10-13", "stance": "recommend", "quote": "Rust + Axum has sort of supported this with a middleware", "excerpt": "Rust + Axum has sort of supported this with a middleware (https://github.com/lazear/axum-aws-lambda). Essentially you write your API as normal, and then when you build for lambda you enable a feature that does the special handler for you. This + Function URL + Cloudfront, and you end up with an API entirely hosted in lambda. I have a backend that does is hosted like this that does pretty complex work (image/video upl", "context": "", "use_case": "web API framework", "switched_from": "", "story": "AWS Lambda Web Functions"}, {"id": 801052482, "item_id": 50065780, "url": "https://news.ycombinator.com/item?id=50065780", "by": "brainless", "date": "2026-10-13", "stance": "neutral", "quote": "Auxum/Actix Web", "excerpt": "I remember CGI days and I have written tiny web \"features\" with Perl and C many years ago. All my product backends are now in Rust and SQLite but I use frameworks and libraries. Like Tokio, Auxum/Actix Web, Diesel. I am not sure I like the idea that the binary will be called by nginx on each request. I prefer the backend binary to have state. A 256 MiB virtual instance is enough for any software shared between friend", "context": "builds product backends in Rust", "use_case": "Rust web backends", "switched_from": "", "story": "A Modern Web App in C"}, {"id": 798190225, "item_id": 49886889, "url": "https://news.ycombinator.com/item?id=49886889", "by": "dgroshev", "date": "2026-09-29", "stance": "warn", "quote": "Fragile boilerplate.", "excerpt": "Fragile boilerplate. I love \"Zero to Production in Rust\", but that's a pretty long book that recreates a fraction of what comes out of the box with Django. Also, when things come with Django, there's no need to maintain or worry about subtle yet crucial bugs.", "context": "", "use_case": "ecommerce/CRUD web apps", "switched_from": "", "story": "What About Rails?"}, {"id": 797570322, "item_id": 49848145, "url": "https://news.ycombinator.com/item?id=49848145", "by": "dysoco", "date": "2026-09-25", "stance": "compare", "quote": "there's no way I'm going to choose Rust+Axum as much as I love Rust for an ecommerce/CRUD", "excerpt": "But they fill different niches, there's no way I'm going to choose Rust+Axum as much as I love Rust for an ecommerce/CRUD vs something as batteries-included and expressive like Rails or Django.", "context": "", "use_case": "ecommerce/CRUD apps", "switched_from": "", "story": "What About Rails?"}, {"id": 743530691, "item_id": 46470668, "url": "https://news.ycombinator.com/item?id=46470668", "by": "positron26", "date": "2026-01-02", "stance": "neutral", "quote": "We use Leptos, Axum, Postgres with SQLx.", "excerpt": "Positron | Bootstrapping Startup | South Korea | Co-founder Equity-only co-founders. If you must take a salary position, send us a resume with \"Salary only\" and we'll check back later. We're developing an efficient social-decision model so that communities can organize social-finance campaigns and effectively administrate funds without being beholden to one creator. Keeping funds in the hands of backers creates accou", "context": "", "use_case": "web server framework", "switched_from": "", "story": "Ask HN: Who is hiring? (January 2026)"}]}