3 ms·
Hear me out: Django for database modeling and the free admin, then the API fronting your service in Rust (actix-web, or your choice), with whatever frontend you
by Klonoar 5y ago
Hear me out: Django for database modeling and the free admin, then the API fronting your service in Rust (actix-web, or your choice), with whatever frontend you feel fits you best.
Django's database modeling (using just that) gives you migrations and some form of typing that take you quite far. You're doing the API on querying on the Rust side, so the ORM isn't really a big concern. The admin can also take you quite far and is incredibly useful for giving others access to view and/or modify data if you need to.
This is also relatively easy to decouple if you need to scale.
- coffeefirst 5y agoBetter yet, use Django (or Rails) with a simple distributed frontend until you need anything else.
- Klonoar 5y agoTotally a valid option as well. I personally prefer Rust's strict environment and find I build better that way, which is why I go this route. I find the trade-off to be acceptable but YMMV, as always. :)
- coffeefirst 5y agoAbsolutely. I’d be curious to see what a rust api layer like this looks like in practice.
- cpursley 5y agoYou can get all of that plus some with Supabase or Hasura without having to write a single model or resolver, all on top of rock solid Postgres. And hook up Appsmith if you need custom admin.