3 ms·
I am so looking forward to all the micro-services disaster stories guaranteed to appear in the future. A friend of mine is already deep in a 20 year old micro-s
by mbrodersen 4y ago
I am so looking forward to all the micro-services disaster stories guaranteed to appear in the future. A friend of mine is already deep in a 20 year old micro-services mud pile. If you think a spaghetti monolith is bad, just wait until you encounter a 100+ micro-services spaghetti monster. My WTF record has reach dizzying now heights just listening to my friend talking about a few of the problems he encountered working on it.
- abraxas 4y agoI left my last job as a senior architect mostly because of microservices ran amok. I decided that there was little I could do to move the needle and since the microsevice mania drove them also to having close to a hundred of those things there wasn't a way to make a meaningful contribution other than tell them to throw it all in the garbage and start over with a vastly simplified architecture.
- mbrodersen 4y agoYep not surprised. The reality is that most micro-services only work OK today because they are basically a complete rewrite of the previous system or a brand new system. ANY brand new system (including monoliths) works perfectly fine because it is all new and everything is in the developers heads. Just wait a few years and the system will turn into not only spaghetti but distributed spaghetti as new developers join the team and the original writers of the system leave.