3 ms·
That's ridiculous. Just don't break anything, ever. If you need a service to behave differently, you give it a different name and roll it out and wait for tra
by thedance 7y ago
That's ridiculous. Just don't break anything, ever. If you need a service to behave differently, you give it a different name and roll it out and wait for traffic on the original to fall to zero and then you wait a bit longer and them you turn it off and delete it. People who advocate for versioned services just do. not. get it.
- dikei 7y agoEhh, what you just described is often how service versioning works: launch a v2 service with the v1 still active, keep them running concurrently for a while, then turn off the v1 when it's no longer used. You can distinguish the versions by using different endpoints, version fields, version headers, etc.. But that's just implementation details.