4 ms·
Microservices can be okay, but they are greatly overused. They are a solution for very large organizations with a ton of teams. For 100 micro-services to make a
by TheCoelacanth 6y ago
Microservices can be okay, but they are greatly overused. They are a solution for very large organizations with a ton of teams. For 100 micro-services to make any sense at all, you need to have at least 200-300 developers.
Total rewrites, on the other hand, are never anything other than a complete and unmitigated disaster. The only way that you can possibly make a $100M rewrite successful is to do it Ship of Theseus style, where the rewritten code is incorporated into the working and actively-used production software long before the full rewrite is complete.
Even then, the full rewrite usually won't complete, so you need to make sure that project is still useful even if you only do a partial rewrite.
- TwoBit 6y agoHas there ever been a large scale successful rewrite? How much of Netscape/Firefox was rewritten from the ground up?
- eloff 6y agoFull rewrites are usually almost always a disaster. I should know, I've done a few on side projects. This case was a dramatic example of that. > For 100 micro-services to make any sense at all, you need to have at least 200-300 developers. Yeah, at minimum. I think these guys were running at least 2 microservices per developer. That made no sense to me.
- justin_oaks 6y agoI've heard of the "Ship of Theseus" rewrites as a recommendation for "evolution, not revolution". I agreed that the big rewrite (i.e. "revolution") is usually a disaster.