3 ms·
So if I worked at Google and in my library/service provided a versioned API what would happen? Would I be told off? Do people do this? Eg, /v1/dosomething, I n
by jarofgreen 5y ago
So if I worked at Google and in my library/service provided a versioned API what would happen? Would I be told off? Do people do this?
Eg, /v1/dosomething, I need to make a breaking change but I can still provide the old service too so I leave v1 alone and instead add /v2/dosomething
- deleted 5y ago[deleted]
- sagarm 5y agoThe article is talking about direct source dependencies, not service dependencies. Services have to be backwards compatible or provide a migration period (of course, there's no real alternative). Sort of similar to your /v2/. If you as a service provider really want to support N versions of your service, you could in theory have multiple instances of your service on different versions. Sounds like an ops and usability nightmare to me though. Clients must be rebuilt every few months so services do not have to support old clients indefinitely, so as a service provider you can rely on a reasonably well constrained migration period.