re: The Rails Ecosystem is Healthier than Ever VIEW POST

TOP OF THREAD FULL DISCUSSION
re: a microservice architecture is just a monolith broken up into smaller apps. I think that's more a result of people doing microservices because it...

To be fair, I do see the benefits of microservices in the right scenario.
They allow for small, independent teams to focus on simple, testable and disposable bits of a greater application and this can help reduce time-to-market and embrace continous delivery when building complex and intricated systems.

I worked on a not-quite-microservices-but-still-service-oriented project and it was fun, bits of the application can go online without worrying about the others (we used message queues to decouple them). But it surely was complex to handle and maintain compared to a monolithic application.

Which is why a said "a majority of web apps don't need a micoservice architecture", not "no web app needs a microservice architecture". 😉 But that need emerges as a system grows and shouldn't be assumed from the get-go. Nothing is stopping you from using a message queue to decouple parts of your monolith, which gives you most of the same benefits without any of the incidental complexity.

code of conduct - report abuse