Protocol Buff Versioning with microservices

[anand]

Team,

How can i achieve the versioning in protocol buffer , I have one use cases where if the version of the microservice change how version of the protobuff can be managed 

Regards
Anand 

[Alex Van Boxel]

Hi,

As long as you schema doesn't change, or change in a compatible way you should not change a version. Protobuf is build for evolution. If you need to make braking changes you should create a new version. A good guideline for how to version is looking at the Google API Design Guidelines:

https://cloud.google.com/apis/design/versioning

It has a specific section about versioning. You have also various tools to guard against braking changes, this can be build into your CI/CD pipeline:

Prototools: https://github.com/uber/prototool

Protolock: https://github.com/nilslice/protolock

I'm going to inject a shameless plug for the tool that we are building, a schema registry for protobuf/grpc. We're hard at work to get it production ready, but I think it's better to look at the above tools first:

https://github.com/anemos-io/metastore

Also note that versioning your contracts should be decoupled from the versioning of your microservice. I hope this helps.

 _/
_/ Alex Van Boxel

--
You received this message because you are subscribed to the Google Groups "Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+u...@googlegroups.com.
To post to this group, send email to prot...@googlegroups.com.
Visit this group at https://groups.google.com/group/protobuf.
To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/e6f89f11-0ed8-4867-863a-4b54a72550b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.