shelf VS aqueduct

Most of them are using shelf or http_server as backend, not sure if it's really necessary to test them all one by one. Anyway, I will use shelf for one reason: this is not a framework, and it is maintained by the Dart team. I'm a bit sad though, because I can't find a lot of documentation, except the official API. To use WebSocket with shelf, the shelf_web_socket handler is required, again, only the API documentation can easily be found. A full example can be found in server/simple directory from dart source code.

Shelf — Simple for APIs.

Dart's potential for backend development has gained a lot of attention. While Dart's official shelf library has been the traditional solution for backend development, there has been other solutions to enable full-stack Dart applications. Projects like Serverpod and Dart Frog are expanding the ecosystem, making it easier than ever to build complete applications using Dart on both frontend and backend.

Shelf

To be honest, there's not much to it! It's a single-file add-on for the shelf package with about 100 lines of code, and the comment for the ProxyHandler class at the top sums up the shelf-proxy package pretty well:

The Dart Language Tour has all of this basic stuff but better, and when you're done, look at the shelf package on pub.dev if you want to get started on creating a server.

These are the best backend frameworks for Dart right now but you can use the shelf package if you want a slightly different approach

In this blog, I will talk about the benchmarks of Flask (Python), Express (JavaScript), Shelf (Dart), dart_frog (Dart) and Conduit (Dart), and my opinions on Dart on the server side.

Thats all what I found - https://github.com/dart-lang/shelf/issues/29 Looks like this is the most recent updated package, not very well know, which can handle cookies - https://pub.dev/packages/shelf\_secure\_cookie

There was a time, I want to start a new project and have to choose what technologies to use for the frontend and backend parts as well. Research gets me to Aqueduct and Shelf, both of them weren't looking actively developing and supported and that leads me to the idea to make my own small micro-framework like Echo for Golang or Bottle for Python. And it was easy to decide: I've had time and motivation :)

Why not just find new maintainer for Aqueduct or Angel ? Or pull out a reusable ORM package from them ?

Saw this about Aqueduct also losing support as it is tough to move to null-safe. https://github.com/stablekernel/aqueduct/issues/917#issuecomment-783700669

From - https://github.com/stablekernel/aqueduct/issues/917

https://github.com/stablekernel/aqueduct/issues/917#issuecomment-783700669

Agreed, it is also more on brand with the website to use Dart for our backend. As for graphql support, aqueduct afaik currently does not have graphql support as per this issue. If we are to use graphql, angel looks like a good option. Otherwise we have to fallback to REST instead.