3 ms·
Main challenge with this approach is change management of models scheme. Apart from Consensus for updating schema, maintaining versioned models across services
by praveen9920 1y ago
Main challenge with this approach is change management of models scheme. Apart from Consensus for updating schema, maintaining versioned models across services becomes a challenge. Let’s say someone deprecates a field in schema, all services needs to update the business logic based on that which is challenging and against the ethos of distributed services.
- regularfry 1y agoIt's a challenge but in principle it's doable with contract testing, in the style of Pact, where there's a contract broker that disparate services all coordinate through. If you've got that, you can publish your new model version as a new contract version, and everyone can see immediately where their APIs need to change. Contracts do get a passing mention in the article, but it's not a focus.
- detaro 1y agoIt's still distributed services in the service of one entity. So why is something deprecated without a clear plan what existing users will do? To me feels related to the monorepo or not discussions?