3 ms·
You didn't understand what I wrote. I said that having interdependent services the way the diagram was drawn leads to an extremely fragile system. If one servic
by jennyyang 7y ago
You didn't understand what I wrote. I said that having interdependent services the way the diagram was drawn leads to an extremely fragile system. If one service goes down, they all go down. It's not a realistic environment or it's a very poorly designed one. If you simplify the diagram to one that is more realistic, with more 1:1 or N:1 relationships, then the combinatorial factor decreases, and then there is no article to write about.
- danielovichdk 7y agoHow does versioning differ based on a 1:1 or a 1:N, or a N:N? It doesn't. No matter how few or many dependencies you have, when they are updated, the dependent system must either update or not update. There is nothing new in regards to versioning of dependencies. It has always been hard to do, and with microservices the versioning story has not all of a sudden improved. What people that are new to versioning, seen from a somewhat autonomous systems perspective, this is something you must have a strategy for.