https://www.jikkou.io/docs/comparisons/Recent content in How Jikkou Compares on JikkouHugoenhttps://www.jikkou.io/docs/comparisons/jikkou-vs-terraform/Mon, 01 Jan 0001 00:00:00 +0000https://www.jikkou.io/docs/comparisons/jikkou-vs-terraform/<div class="alert alert-primary" role="alert"> <h4 class="alert-heading">TL;DR</h4> Use <strong>Terraform</strong> when Kafka is one of thirty resource types you provision (clusters, networks, service accounts, API keys). Use <strong>Jikkou</strong> when you manage what lives <em>inside</em> Kafka: hundreds of topics, ACLs, quotas, and schemas that must stay reconciled against the real cluster, not against a state file. Many teams use both: Terraform provisions the cluster, Jikkou manages its contents. </div> <h2 id="the-state-file-problem">The state-file problem</h2> <p>Terraform trusts its state file. Kafka clusters do not stay in sync with state files.</p>https://www.jikkou.io/docs/comparisons/jikkou-vs-strimzi/Mon, 01 Jan 0001 00:00:00 +0000https://www.jikkou.io/docs/comparisons/jikkou-vs-strimzi/<div class="alert alert-primary" role="alert"> <h4 class="alert-heading">TL;DR</h4> If your Kafka clusters run on Kubernetes under <strong>Strimzi</strong>, keep the <strong>Topic Operator</strong> for topics; it is the right tool there. Use <strong>Jikkou</strong> for everything it cannot reach: Schema Registry subjects, Kafka Connect connectors, ACLs and quotas at breadth, Confluent Cloud, Aiven, Amazon MSK, and any cluster that does not live in your Kubernetes estate. If you are <strong>not</strong> on Kubernetes, the Topic Operator is not an option at all, and Jikkou covers the whole surface on its own. </div> <h2 id="two-different-jobs">Two different jobs</h2> <p>The cleanest way to see the difference: <strong>Strimzi runs Kafka; Jikkou manages what is inside it.</strong></p>