4 ms·
Just because something can be done, including the fashionable microservices "architecture", it does not mean that it should be done, or that it is a good idea.
by Fins 9y ago
Just because something can be done, including the fashionable microservices "architecture", it does not mean that it should be done, or that it is a good idea.
- ChicagoDave 9y agoApplication architecture is inherently malleable, yes. But when properly implemented, micro service architecture is actually a great idea. I can’t help if your experience has not been the same as mine.
- Fins 9y agoCertainly, one can architect anything, use NoSQL for critical data storage, or use Kafka for synchronizing two SQL databases with the same schema and living on the same netowrk(an actual proposal from a fan of microservices, btw). But whether it should be done is another question, and I have yet to see a single example of microservices being a good idea. Not "it works" -- obviously, you can get it to work, but being better than alternatives. Come to think of it, Mongo is the same...
- ChicagoDave 9y agoThe Accenture link I posted is a living example of a highly successful micro-services architecture in a critical internal application in a large corporation. What more do you want?