3 ms·
I think Rails would be an excellent choice here. Lots of Gems and community and enterprise support. A lot of bigwigs use Rails for their production services. A
by arkokoley 9y ago
I think Rails would be an excellent choice here. Lots of Gems and community and enterprise support. A lot of bigwigs use Rails for their production services.
Admin panel, tagging, search, you have gems for practically any functionality you might need.
If you want to do some hardcore PWA and SPA stuff, you have webpack built in rails through the webpacker utility. Go crazy!
- dotNEET 9y agoThanks for the advice. I had built out a small application in dotnet core mvc and rails to get a taste of how both of them are currently structured. Rails OOP and dynamism allows for some less verbose abstractions which I like (I'm not afraid of the magic, the rails source seems pretty legible), but dotnet MVC has some nice things like async built in, and feature-full job queueing without paying $1k per year. Those are my initial impressions. I'd be glad to update my knowledge if I'm wrong.
- arkokoley 9y agoI haven't had any experience with dot net MVC, but a feature full job queuing is present in Rails through the ActiveJob module. If that falls short, you can always use Sidekiq. We regularly use Sidekiq for all of our Async tasks at Zense.