APIs are forever. Or at least they feel that way. Once an endpoint is published, it will be called by systems you’ve never met, in environments you’ll never control, for longer than you ever intended. This is why API deprecation is one of the hardest decisions an architect faces.
If you change a database column, you only affect your own team. If you change a REST endpoint, you affect production systems run by other people like partners, customers, unknown consumers who found your API years ago and quietly built on it. Breaking them may mean contractual penalties, legal disputes, or at the very least, angry emails at 3 a.m.
Read the full post on https://www.the-main-thread.com/p/when-to-deprecate-apis-java-quarkus-guide
Top comments (0)