3 ms·
Rails is a great monolith framework, but a monolith will eventually reach its limits, due to size/complexity of the team or the task at hand. I think providing
by jmchuster 8y ago
Rails is a great monolith framework, but a monolith will eventually reach its limits, due to size/complexity of the team or the task at hand. I think providing a better story around how to prepare for or handle that transition would definitely serve Rails a lot better in the long run. But, as long as the main target audience of Rails is Basecamp (a saas tool with 12 developers), I don't see it in the future.
- dymk 8y agoThe company I work at is transitioning from a rails monolith to many smaller rails micro services - it’s the best if both worlds.
- joelbluminator 8y agolol good luck with that. the main thing that makes this work is that the company trying micro services most likely grew large and now has a big engineering team. It also moves slower than it used to due the stage it's in. In that case any architecture would work really...you have a huge team of engineers that moves slowly and can troubleshoot whatever issues arise. yay to micro services!
- batiste 8y agoI think the best is to have nicely designed modular monolith application. Sadly this something that Rails backwards conventions makes very hard to achieve.