Hello everyone, we are currently trying to improve the management of our topic configurations. At the moment we are managing the configurations on the producer side and checking/creating/changing topics on each application (instance) startup.
This has worked fine for many cases, but does not really protect against duplicate/conflicting configuration and also requires handling of concurrency issues. On the plus side, this makes it easy for different teams to handle the configurations for "their" topics. A more centralized approach would fix some of those problems but would create other dependencies on the deployment side. I'm very interested in any feedback you can provide how you manage the topic configuration and changes in your systems, especially regarding versioning (of the configuration, not content). best regards Patrik
