3 ms·
> We cant simply bring up the latest version of "microservice A" This should not be the case. Build your services to be backwards compatible. Avoid making brea
by BillinghamJ 11y ago
> We cant simply bring up the latest version of "microservice A"
This should not be the case. Build your services to be backwards compatible. Avoid making breaking changes, but when you do, make a new API version & maintain the previous one until it's no longer used.
i.e. /v1/blah
-- breaking change introduced --
/v1/blah - maintains backwards compatible behavior
/v2/asdf - new behavior exposed as v2, update microservice B at some point in the future to use this
- supermatt 11y agoWe have contracts to ensure API compatibility. That means we CAN simply rip out the old API and put in a new one, but the integration will fail until the consumer contracts sync up. As these are internal services (microservices) that only we consume, there is no need to keep old cruft around.