Databases · head to head
etcd vs Flowable

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No

Flowable
Automation Integration
Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti
- From
- Free
- Free plan
- Yes
The short version
- Flowable is free; etcd prices on request.
- Only etcd lists raft consensus; only Flowable lists BPMN 2.0 engine.
- Where Flowable falls short: enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
- Prices and features on this page were last checked on 13 November 2026.
How do etcd and Flowable differ?
etcd and Flowable differ on starting price (On request against Free), pricing model (Open-source against Quote) and free tier (No against Yes). Only the attributes on which etcd and Flowable actually diverge.
Which features does each one have?
They share no listed features; 8 appear only for etcd and 8 only for Flowable. 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 Flowable
- BPMN 2.0 engine
- CMMN case management
- DMN decision tables
- Spring Boot integration
- Modelling studio
- Task and case application
- REST APIs
- History and audit
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 Flowable
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Flowable
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Flowable
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Flowable
Flowable
- An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot etcd
- A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot etcd
- A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot etcd
- A regulated organisation needing complete process history and decision table audit trails for supervisorsnot etcd
Where do etcd and Flowable 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
Flowable
- The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it
- It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical
- Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives
- The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one
- Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe
How much do etcd and Flowable cost?
Flowable is free to use. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
Flowable
Free- Flowable Open SourceFree
- Apache 2.0 licensed BPMN, CMMN and DMN engines
- Embeddable Java library or standalone apps
- No modelling studio or enterprise applications
- Flowable EnterpriseOn request
- Modelling studio, work application and admin console
- Connectors, forms and advanced identity management
- Support with SLA and version maintenance
Which should you pick?
Choose Flowable if
- You need bpmn 2.0 engine.
- You want to start without paying.
- You work on Linux, Windows, Self-hosted, Web.
- You also want cmmn case management.
Questions people ask
- Is etcd or Flowable better?
- Neither clearly leads. etcd starts at On request and Flowable at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Flowable?
- Flowable has a free tier; the other does not. Paid plans start at On request for etcd and Free for Flowable.
- Does etcd or Flowable run on more platforms?
- etcd runs on Web. Flowable runs on Linux, Windows, Self-hosted, Web.
- Can I use Flowable for free?
- Yes. Flowable 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 Flowable is typically brought in for.
- What can etcd do that Flowable cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration.
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.
Flowable: Is Flowable open source?
Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.
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.
Flowable: How does it relate to Activiti and jBPM?
The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.
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.
Flowable: What does Flowable Enterprise cost?
Nothing is published. It is quoted per deployment by the vendor.
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.
Flowable: Why choose it over Camunda?
CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.
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.
Related pages
Other head to heads
- etcd vs DynamoDB
- etcd vs Timeplus
- etcd vs Firebase Realtime Database
- etcd vs Knack
- etcd vs Turso
- etcd vs BigQuery
- etcd vs TiDB
- etcd vs Dgraph
- etcd vs turbopuffer
- etcd vs Apache Kafka
- etcd vs Redis
- etcd vs Postgres
- etcd vs Presto
- etcd vs Privacera
- etcd vs RavenDB
- etcd vs Readyset
- etcd vs Redpanda
- etcd vs Apache Airflow
- etcd vs Temporal
- etcd vs Nintex
- etcd vs jBPM
- etcd vs Activiti
- etcd vs Camunda
- etcd vs Kogito
- etcd vs Airbyte
- etcd vs Meltano
- etcd vs Hatchet
- etcd vs Nango
- etcd vs Windmill
- etcd vs RudderStack
- etcd vs Workato
- etcd vs Automation Anywhere
- etcd vs Blue Prism
- etcd vs CrewAI
- etcd vs Mage AI
- etcd vs mParticle
- Flowable vs DynamoDB
- Flowable vs Timeplus
- Flowable vs Firebase Realtime Database
- Flowable vs Knack
- Flowable vs Turso
- Flowable vs BigQuery
- Flowable vs TiDB
- Flowable vs Dgraph
- Flowable vs turbopuffer
- Flowable vs Apache Kafka
- Flowable vs Redis
- Flowable vs Postgres
- Flowable vs Presto
- Flowable vs Privacera
- Flowable vs RavenDB
- Flowable vs Readyset
- Flowable vs Redpanda
- Flowable vs Apache Airflow
- Flowable vs Temporal
- Flowable vs Nintex
- Flowable vs jBPM
- Flowable vs Activiti
- Flowable vs Camunda
- Flowable vs Kogito
- Flowable vs Airbyte
- Flowable vs Meltano
- Flowable vs Hatchet
- Flowable vs Nango
- Flowable vs Windmill
- Flowable vs RudderStack
- Flowable vs Workato
- Flowable vs Automation Anywhere
- Flowable vs Blue Prism
- Flowable vs CrewAI
- Flowable vs Mage AI
- Flowable vs mParticle
