3 ms·
unless the update requires version updates on multiple services which means the versioning and rollback has the same effect as a more monolithic codebase. but w
by interactivecode 3y ago
unless the update requires version updates on multiple services which means the versioning and rollback has the same effect as a more monolithic codebase. but with the added complexity of not knowing how it all impacts each other.
In my experience updates to smaller services are often trivial, or for updates that are actually impactful it would be way easier to coordinate in a monolithic codebase.
- steveBK123 3y agoyes my first job over 15 years ago was essentially micro services, and we ran into this type of problem.. trivial updates to individual services could be iterated extremely quickly systematic changes to behavior across services were so hard they became incredibly uncommon