<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Topics on Devops Monk</title><link>https://devops-monk.com/tags/topics/</link><description>Recent content in Topics on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/topics/index.xml" rel="self" type="application/rss+xml"/><item><title>KafkaAdmin and AdminClient: Managing Topics Programmatically</title><link>https://devops-monk.com/tutorials/spring-kafka/kafka-admin/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/spring-kafka/kafka-admin/</guid><description>Why Manage Topics Programmatically? CLI commands work for one-time setup. Production services need:
Startup validation — verify required topics exist before the application starts Auto-provisioning — create topics at deployment time with correct config Dynamic tenant onboarding — create per-tenant topics at runtime Config drift detection — compare actual topic config against expected values Spring Kafka provides KafkaAdmin for declarative topic management and AdminClient for imperative operations.
KafkaAdmin — Declarative Topic Creation Declare NewTopic beans — Spring Kafka creates them at startup if they don&amp;rsquo;t exist:</description></item></channel></rss>