The latest articles on DEV Community by Vladimir (@vladada). https://dev.to/vladada https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F377805%2F099b4b9b-9634-4ca8-8aba-4719418f07a7.png https://dev.to/vladada en Vladimir Sat, 02 May 2020 01:08:56 +0000 https://dev.to/vladada/how-to-handle-kafka-schema-management-among-many-developers-3bd4 https://dev.to/vladada/how-to-handle-kafka-schema-management-among-many-developers-3bd4 <p>On a project with many developers and different environments (local, develop, qa, production), what kind of processes/tools need to be implemented in order to avoid compatibility issues either during CI or later when making release?</p> <p>I can't seem to find any guidelines/best practices about this on the web.</p> <p>I am leaning towards a solution where developers validate and register new schemas against production Schema Registry. Maybe even creating some web application using Schema Registry REST API to show all schema versions and having ability to edit schema, validate changes (syntax and compatibility) and register new version. Then somehow replicate all new schema versions to other qa and develop environments.</p> <p>There are other approaches like keeping schemas inside git repository.</p> <p>What do you think?</p> discuss help kafka