Lawrence, There are two common ways to approach registration of schemas. The first is to just rely on auto-registration that the serializers do (I'm assuming you're using the Java clients & serializers here, or an equivalent implementation in another language). In this case you can generally just allow the registration to happen as the updated application hits each stage. If it gets rejected in staging, it won't ever make it to prod. If you discover an issue in staging, the most common case is that it isn't a problem with the schema but rather with the surrounding code, in which case a subsequent deploy will generally be able to succeed. Note that unrelated changes can continue even if you end up not deploying the change to production since they will not be affected by the newly registered schema.
The second way is to build the registration into your deployment pipeline, so you may perform the registration before ever deploying an instance of the app. This generally requires more coordination between your deployment and apps (since deployment needs to know what schemas exist and how to register them in the appropriate environment), but allows you to catch errors a bit earlier (and may allow you to restrict writes to the schema registry to the machines performing deployment, which some shops may want to do). One of the goals of the schema registry is to help decouple developers within your organization, so it is absolutely common for developers to simply create new schemas. In fact, they may just build the entire process into their app. For example, while not released yet, we have a maven plugin that you can use to integrate interactions with the schema registry into your Maven/Java application development process: https://github.com/confluentinc/schema-registry/tree/master/maven-plugin -Ewen On Mon, Sep 26, 2016 at 1:33 PM, Lawrence Weikum <lwei...@pandora.com> wrote: > Hello, > > Has anyone used Confluent’s Schema Registry? If so, I’m curious to hear > about best practices for using it in a staging environment. > > Do users typically copy schemas over to the staging environment from > production? Are developers allowed to create new schemas in the staging > environment? > > Thanks! > > Lawrence Weikum > > -- Thanks, Ewen
