> But with microservices you have more supposed independent interfaces.
You don't. You have more services accessed over a network, and might not have control over all services. But that's already par for the course in nonoliths.
If you were to refactor your components by changing classes around (say, a major version update in a dependency) while not updating the components that used them then you would also have problems.
That's why versioning and service discovery and HATEOAS are a thing.
You don't. You have more services accessed over a network, and might not have control over all services. But that's already par for the course in nonoliths.
If you were to refactor your components by changing classes around (say, a major version update in a dependency) while not updating the components that used them then you would also have problems.
That's why versioning and service discovery and HATEOAS are a thing.