4 ms·
You version your APIs, but do you version your services ? Think of your new service as having a different deployment target, its own DB, and could be under a d
by makeitdouble 4y ago
You version your APIs, but do you version your services ?
Think of your new service as having a different deployment target, its own DB, and could be under a different repo altogether.
- 0x457 4y agoSo? Have you heard of API Gateway and/or HTTP routing based on path prefix or header?
- makeitdouble 4y agoYou're right about the external interface, but you still need to give a name to the actual service behind the URL. From your point on versioning, I'd assume you'd actually call it UserProfileV2 ? PS: to get back to the original point, you're still stuck with a "UserProfileV2" service that does a lot more than just user profiles, but that's not reflected in the name.
- 0x457 4y agoIt depends on the language, but I would probably call it `UserProfile` and change a major version even if it's in an entirely different language. Maybe even kept in the same repo. > PS: to get back to the original point, you're still stuck with a "UserProfileV2" service that does a lot more than just user profiles, but that's not reflected in the name. From what it said in the original comment, it still seems like a user profile to me.
- qaq 4y agoYou def don't want a new DB and for it to be under new repo