4 ms·
Microservices actually allow teams to work independently of each other (once there are agreed on interface contracts) and more importantly, decouple schedule -
by efitz 5y ago
Microservices actually allow teams to work independently of each other (once there are agreed on interface contracts) and more importantly, decouple schedule - I don't have to wait or switch to something else if you're 3 days late delivering your component; it is usually easy to mock the inputs and outputs and build test harnesses and do lots of things that are more difficult with monoliths.
HOWEVER, I don't understand why people get religious about methodologies. Every time a new fad comes out, I don't look at it as the "One True Way", I just evaluate its strengths and weaknesses and add it to my toolbox. I also am not religious about following all the precepts of the new religion. I'll mix agile and waterfall if I want. I will conduct my daily status meetings how I want and call them scrum, even if it's just to piss off zealots. I will sit down during standup. I'll mix microservices and monoliths. I will figure out the value I want from a methodology and be happy when I get that; I don't believe in utopia anymore.
- mixedCase 5y ago> I don't have to wait or switch to something else if you're 3 days late delivering your component; it is usually easy to mock the inputs and outputs If you know the spec for inputs and outputs, wouldn't you be able to do the exact same in a monolith?
- efitz 5y agoDepends on merging, etc. A lot of times when you develop monolithically you develop in different branches and some of your pieces won't show up until the next merge. You can unit test but can't integration test in many cases.