4 ms·
Exactly! I think we completely agree. All those reasons are very fine ones - but it's still a dangerous move to go microservice style. You have to know what yo
by friendly_chap 9y ago
Exactly! I think we completely agree.
All those reasons are very fine ones - but it's still a dangerous move to go microservice style. You have to know what you are doing, and in our buzzword driven industry that's not the case usually.
Little insidious time wasters will creep into your work flow and they will lurk there eat away dollars and you won't even notice.
I constantly switch back and forth between working on monolithic and microservice apps and for the majority of companies sticking to a monolith until the pain points you mentioned become unbearable is the good call.
Even then, just break down your apps to bigger sized services, and stop when the pain goes away. Microservices is a catchy name but if anything micro is the poison there.
- je42 9y agoyeah good to point to make it explicit. splitting to smaller (but not micro) is a very good transition, that might already help.
- afpx 9y agoGiven that I have been part of a team that independently invented micro-services, and that since knowing that, I’ve met several other people who have done similarly, it can’t imagine that it’s all that hard. To me, it was just a natural evolution. What do you consider as the most important things that people are do wrong? Also, could you enumerate the time-wasters? Off hand, besides occasionally having to re-consolidate the architecture, I can’t think of many. It would be good to know how much the time-wasters cost in contrast to the alternatives.