Softwr

Databases · head to head

etcd vs Kogito

etcd logo

etcd

Databases

A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.

From
On request
Free plan
No
Kogito logo

Kogito

Automation Integration

Cloud-native business automation for Quarkus, now an Apache KIE component

From
Free
Free plan
Yes

The short version

  • Kogito is free; etcd prices on request.
  • Only etcd lists raft consensus; only Kogito lists build-time code generation.
  • Prices and features on this page were last checked on 13 November 2026.

How do etcd and Kogito differ?

etcd and Kogito differ on starting price (On request against Free), pricing model and free tier (No against Yes). Only the attributes on which etcd and Kogito actually diverge.

Attributes where etcd and Kogito differ
AttributeetcdKogito
Starting priceOn requestFree
Pricing modelOpen-sourceOpen source, no licence fee
Free tierNoYes
PlatformsWebLinux, Self-hosted
CategoryDatabasesAutomation Integration

Which features does each one have?

They share no listed features; 8 appear only for etcd and 6 only for Kogito. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in etcd

  • Raft consensus
  • Linearizable reads
  • Transactions
  • Leases
  • Watches
  • MVCC revision history
  • Role-based access control
  • Snapshot backup and restore

Only in Kogito

  • Build-time code generation
  • Quarkus and Spring Boot support
  • DMN decision services
  • Drools rules engine
  • Serverless workflow
  • Kubernetes operator

What is each one used for?

etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL. The jobs each tool is most often brought in to do.

etcd

  • Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot Kogito
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Kogito
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Kogito
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Kogito

Kogito

  • A Quarkus microservice that must expose a DMN decision model as a REST endpoint with millisecond start-upnot etcd
  • Serverless deployment of business rules where a traditional BPM server would be far too heavynot etcd
  • A Red Hat shop that wants the upstream of Red Hat process automation with the option of a supported build laternot etcd
  • Replacing hand-coded conditional logic with DMN tables that business analysts can review and amendnot etcd

Where do etcd and Kogito fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

etcd

  • It is sized for coordination data, not application data: the default backend quota is 2 GB and 8 GB is the documented recommended maximum, and exceeding it puts the cluster into a NOSPACE alarm where it accepts no writes until an operator compacts, defragments and clears the alarm by hand
  • Every write is replicated and fsynced before acknowledgement, so cluster performance is bounded by the slowest disk in it; a member on network-attached storage with high fsync latency causes leader elections and cluster-wide latency spikes that look like network problems and are not
  • Adding members increases availability but reduces write throughput, because each write must reach a larger quorum; you run three or five members for fault tolerance, and increasing capacity means faster hardware rather than more nodes
  • There is no sharding and no multi-tenancy, so isolating workloads means running separate clusters, each with its own quorum, certificates, backup schedule and upgrade path, and that operational multiplication is often unexpected
  • Running it yourself is a real job: periodic compaction and defragmentation, snapshot backups you have actually rehearsed restoring, and rotation of both peer and client TLS certificates, none of which happens automatically outside a managed Kubernetes service
  • Losing quorum is not self-healing; recovering a cluster that has lost a majority means restoring from a snapshot and accepting that everything written since that snapshot is gone, which makes backup frequency a data-loss budget decision rather than a routine setting

Kogito

  • Kogito is a developer framework, not a product, so there is no equivalent of Camunda Operate for business users and any process monitoring interface has to be built or bought separately
  • Long-running stateful processes need external persistence and messaging that you configure and operate yourself, which removes much of the convenience a BPM server normally provides
  • It sits inside the Apache KIE incubator, and incubating status means graduation is not guaranteed and the project name and artefact coordinates have already changed once
  • Red Hat is by far the dominant contributor despite ASF stewardship, so the roadmap follows Red Hat product priorities rather than community demand
  • Documentation is spread across legacy JBoss sites, the old Kogito site and the new Apache KIE site, and search results routinely land on outdated versions, which costs real time during adoption

How much do etcd and Kogito cost?

Kogito is free to use. Plan by plan below, from each vendor's own pricing page.

etcd

On request

No published plan breakdown. See the etcd review.

Kogito

Free
  • KogitoFree
    • Apache 2.0 licence
    • Apache KIE incubating project
    • No usage limits

Which should you pick?

Choose etcd if

  • You need raft consensus.
  • You also want linearizable reads.

Choose Kogito if

  • You need build-time code generation.
  • You want to start without paying.
  • You work on Linux, Self-hosted.
  • You also want quarkus and spring boot support.

Questions people ask

Is etcd or Kogito better?
Neither clearly leads. etcd starts at On request and Kogito at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or Kogito?
Kogito has a free tier; the other does not. Paid plans start at On request for etcd and Free for Kogito.
Does etcd or Kogito run on more platforms?
etcd runs on Web. Kogito runs on Linux, Self-hosted.
Can I use Kogito for free?
Yes. Kogito has a free tier, so you can try it without paying. etcd starts at On request.
What is etcd best used for?
etcd is most often used for storing kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doing, leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactions, service discovery and dynamic configuration where readers need to be notified of changes rather than poll for them, coordinating failover in a clustered database, as patroni does for postgresql. Of those, storing kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doing and leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactions are not what Kogito is typically brought in for.
What can etcd do that Kogito cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Kogito covers Build-time code generation, Quarkus and Spring Boot support, DMN decision services, Drools rules engine.

Answered from the vendors’ own pages

etcd: Can I use etcd as an application database?

No. It is designed for metadata and coordination, with a recommended maximum store size of around 8 GB, no sharding and a write path deliberately optimised for durability rather than throughput. Application data belongs in a database built for it.

Kogito: Is Kogito still maintained?

Yes. It is an Apache KIE incubating project with active commits, with Red Hat as the dominant contributor.

etcd: How many members should a cluster have?

Three for most cases, five where you need to survive two simultaneous failures. Always an odd number, because an even-sized cluster gains no additional fault tolerance while making quorum harder to reach.

Kogito: How does it differ from jBPM?

Kogito compiles process and rule definitions into application code at build time; jBPM was a runtime engine that loads definitions.

etcd: What happens when the store fills up?

The cluster raises a NOSPACE alarm and stops accepting writes, becoming effectively read-only. Recovery requires compacting old revisions, defragmenting each member and then explicitly disarming the alarm, all done by an operator.

Kogito: Does it need Quarkus?

It is designed for Quarkus and supports Spring Boot; both are Java frameworks rather than a standalone server.

etcd: Why is my etcd cluster slow or unstable?

Almost always disk latency. Because every write is fsynced before acknowledgement, slow or shared storage causes heartbeat timeouts, leader elections and cascading latency. Local SSDs with low fsync latency are effectively a requirement.

Kogito: Is there commercial support?

Not from Apache. Red Hat sells supported builds of this lineage as part of its subscriptions.

etcd: How does it compare with Consul or ZooKeeper?

All three provide consensus-backed coordination. etcd has the simplest data model and the Kubernetes ecosystem behind it; Consul bundles service discovery, health checking and a service mesh; ZooKeeper is older, JVM-based and still common under Kafka and Hadoop-era systems.

Share

Related pages

Other head to heads