241–250 of 736 posts
All free, scalability won’t be a problem since it’s a niche app and db r/w work is minimal. I estimate I can support 10k userbase all for free.
I'm going to deploy it on aws fargate sometime in the next 6 months or so, that should get me to scale.
The database I'm going to migrate to a single tiny ec2 instance until I need more resources, then it'll probably go to RDS or PlanetScale.
Earlier quoted context omitted.
Agreed, although I'd really like to throw in type safety, because the lack of it made my life needlessly complicated. Is this feasible with Python?
It’s not enforced at runtime, but otherwise I feel like typing is in a pretty good place in Python right now. If you’re diligent about using Pyright or MyPy as linters it makes life a lot easier.
Disclaimer: I maintain an init tool for this stack so I'm somewhat biased
Hhere is quick survey : Regarding backend choices: curl "https://news.ycombinator.com/item?id=34530052" | grep -i Django | wc -l 36 curl "https://news.ycombinator.com/item?id=34530052" | grep -i supabase | wc -l 17 curl "https://news.ycombinator.com/item?id=34530052" | grep -i rails | wc -l 28 curl "https://news.ycombinator.com/item?id=34530052" | grep -i node | wc -l 15 curl "https://news.ycombinator.com/item?id=345…
Svelte + Typescript & Tailwind, .NET 7, SQLite. Why? Mainly because I'm familiar with them, and would be most productive with these. I'd almost like to reach for Blazor, but if it's at all public-facing, I don't think I can justify using Blazor at this time.
What are your concerns with Blazor for public facing apps?
- Userfront for auth
- Not sure yet about DB/persistence... Supabase? FaunaDB? MongoDB Atlas? Simperium?
However, there are lots of use cases that would call for additional SPA (Vue/Nuxt), or other tech. So in that case I'd add it or replace the tech stack entirely. I'd probably avoid specialized cloud services, might consider something like https://supabase.com tho if the app doesn't need a complex backend.
Because:
- Battle proven
- Secure
- Well maintained
- Well documented
- Fully featured (a lot more than others such as Django or Rails. Jobs, auth, asset manager, etc out of the box)
- Doesn't hate JavaScript, embraces it (hello Rails!).
- The templating system, Blade, is pretty great...you can even do components.
- Opinionated and not that many different ways to do the same thing, makes things more consistent
- Performance is good enough for 99.9% of use cases. For the other 0.01% add Octane.
- Great, friendly and professional community. Top high quality packages with lots of users and well maintained.
- Excellent frontend integration packages in case blade is not your thing: Inertia, Livewire, Hotwire, etc.
- Lots of people know it and like it, so easy to hire for too.
- Code organization makes a lot of sense to me (hello Django!)