The hidden cost of backward compatibility
Anders Sundelin, Javier González‐Huerta, Krzysztof Wnuk · 2020
Context The micro-services architectural pattern advocates for the partitioning of functionality into loosely coupled services, which should be backward compatible, to enable independent upgrades. Deprecation is commonly used as a tool to manage multiple versions of methods or services. However, deprecation carries a cost in that tests might be duplicated and might rely on services that have become deprecated over time.