Multiple versions architecture #2131
-
|
Hey, I have a general architecture question. I see in your example that you hide all endpoints behind Second question is about other dependencies inside the package. What if there is some common code that is only used by v1? Do I just keep increasing common functionalities to enable all versions, or do I just hide the version specific code inside each of the version folders? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Changing api version is not something you would need to do often. To keep things simple I suggest to just use v1 version of api until you will have reason to have v2 which won't be backward compatible. (If v2 will be backward compatible, then maybe you don't need v2). |
Beta Was this translation helpful? Give feedback.
Changing api version is not something you would need to do often. To keep things simple I suggest to just use v1 version of api until you will have reason to have v2 which won't be backward compatible. (If v2 will be backward compatible, then maybe you don't need v2).