On Fri, Oct 30, 2026 at 3:00 PM Reza Jahanbakhshi via Boost < boost@lists.boost.org> wrote:
Hi Christian,
Fair questions, so taking them one at a time:
Compile time and bloat: those should be measured, not assumed. Compile time I'm already working on (see my other mail). Binary size I checked: the hello example in release, stripped, is 1.8 MB with GCC. A hand-written Beast server with the same two routes is 1.1 MB. So taar adds about 0.7 MB on top of Beast, and that includes shutdown and error handling the hand-written one doesn't have. That 0.7 MB is a one-off cost. Each route after that adds about 25 KB (measured up to 52 routes.
Yeah, for the record, I already know Beast/Asio is bloated because I've written a bunch of it, ha ha. You have to take tremendous care to keep both compile time and binary size in check.
Memory safety: true for any C++ server, including everything already built on Beast today. Taar doesn't make anyone pick C++. It helps people who already have.
I guess.
HTTP/1.1: that comes from Beast, not from a decision to give something up. Taar builds on what Boost has and doesn't take anything away. In most deployments HTTP/2 and HTTP/3 end at the load balancer or proxy anyway (AWS ALB, GCP's load balancer, Azure Front Door, Envoy, nginx), and the hop to the app is often plain HTTP/1.1. If Boost gets HTTP/2 support, taar can sit on top of it.
This is true. They basically all terminate HTTP/2 and fall back to HTTP/1. This is actually likely only done because the cost of upgrading existing legacy servers was so high and scaling horizontally is relatively cheap. I'm not sure it's necessarily a ringing endorsement, however, because many of these also support full end-to-end HTTP/2 as well.
JWT, OAuth, etc.: those usually live in a different layer. A gateway or auth proxy (API gateway authorizers, Envoy ext_authz, nginx auth_request, oauth2-proxy) validates the token and forwards the request with the identity in a header. The service reads that header, and taar already matches and extracts headers and cookies. I don't think a routing library should implement OAuth.
Right. So it basically requires significant infrastructure investment and really only works with that. Maybe this isn't such a big deal in practice but I've worked mainly on smaller teams where we haven't done any of that. I'm not sure it's necessarily a valid response to just hand-wave this kind of stuff aside. Maybe other people won't mind, which is fine.
Why not Node, Go, C#...: if you're starting from scratch, maybe. But plenty of teams already have a large C++ codebase and just need an HTTP or REST endpoint in front of it, or even choose to use C++ with new projects. Adding a second language means another runtime, build, deployment and on-call story. That cost is real, and that's the user taar is for.
I guess my question here is, is that really so? Because it sounds like they need a lot more than a REST endpoint. They need a crap ton of Nginx and other proxying services in front just to be usable. So you basically need a devops person. You also kinda lost me on the "another runtime, build, deployment and on-call story". If we're launching a REST service which depends on like 3 other services just to be usable, doesn't that also require being on-call? The level of sophistication you're talking about kind of implies to me that one is already using containerization which makes build deps literally trivial. You just make a new Docker image. Again, if you're already in the world of complex microservice back-end architectures, you have a ton more freedom to choose whichever language you want because everyone already communicates through shared caches like databases and Redis. The language choice genuinely doesn't really matter so it's still really hard for me to see the value in choosing C++ here especially when I don't think Beast/Asio is even particularly fast, especially when you start adding in things like connection timeouts. It sounds more or less like this library is trying to target non-perf-critical scenarios which makes C++ a really tough sell. - Christian