It depends on where that duplication will be located and what level of duplication we are talking about. If we are talking about contracts, then, it is perfectly fine to have duplication. It minimizes risks of errors, and offers a clear separation between versions
Every successful API needs versioning.
It is also a good practice to monitor the number of clients still using older versions and log failed requests that may be due to version mismatches.
That gives guidance about when to sunset old versions.
Great Summary!
appreciate it, thanks Raul!
I appreciate this post. I think I understand better now
How to deal with code duplication when we need to maintain multiple API versions?
It depends on where that duplication will be located and what level of duplication we are talking about. If we are talking about contracts, then, it is perfectly fine to have duplication. It minimizes risks of errors, and offers a clear separation between versions
I enjoy my 2hr