Menu
Back to Discussions

so how do you handle api versioning for microservices?

Wolfgang Schröder
Wolfgang Schröder
·3623 views
Hey everyone, I've been thinking a lot about API versioning recently, especially with microservices. It really feels like there are tons of ways to handle it, you know? Like, you can version in the URL path, use query parameters, custom headers, or even Content-Type negotiation. They all have their upsides and downsides, of course. So, what's your team's go-to method, and what's the reasoning behind it? Have you guys run into any common problems or figured out some good practices the hard way when you're juggling different API versions across your services?
30 comments

Comments

Loading comments...