whichdb
vs

KurrentDB (EventStoreDB) vs PGMQ

KurrentDB (EventStoreDB): A purpose-built event store for event sourcing, with streams, subscriptions and projections. PGMQ: An SQS-style message queue implemented as a lightweight Postgres extension.

key differences

  • KurrentDB (EventStoreDB) is primarily an event store database; PGMQ is relational.
  • Licensing: KurrentDB (EventStoreDB) is source-available (Kurrent License v1 (KLv1)); PGMQ is open source (permissive) (PostgreSQL License).
  • KurrentDB (EventStoreDB) is built for larger datasets (≤ 10 TB) than PGMQ (≤ 100 GB).
  • Transactions: KurrentDB (EventStoreDB) offers limited ACID; PGMQ offers full.
  • Only KurrentDB (EventStoreDB) has change data capture, pub/sub, encryption at rest, role-based access, time travel.

choose kurrentdb for

  • +Event-sourced domain models with CQRS
  • +Audit-heavy financial and logistics systems
  • +Integrating microservices via durable event streams

best at · Event sourcing, OLTP, Pub/Sub

choose pgmq for

  • +Background job queues for Postgres-backed apps
  • +Outbox pattern without a separate broker
  • +Lightweight task queues on Supabase

best at · Queue

KurrentDB (EventStoreDB)A purpose-built event store for event sourcing, with streams, subscriptions and projections.
PGMQAn SQS-style message queue implemented as a lightweight Postgres extension.
overview
Primary model
Event Store
Relational
Also supports
–
–
Type
Database engine
Extension
Status
Active
Active
Developer
Kurrent, Inc.
PGMQ community (originally Tembo)
First release
2012
2023
Latest version
26.2.3 (Oct 19, 2026)
1.13.1 (Oct 20, 2026)
License
Source-availableKurrent License v1 (KLv1)
Open source (permissive)PostgreSQL License
Free tier
✓
✓
popularity
WhichDB Score
18.6
21.1
Rank
#177
#145
GitHub stars
5.9K
5.4K
Stack Overflow questions
185
–
scale & guarantees
Comfortable data size
Medium (≤ 10 TB)
Small (≤ 100 GB)
Horizontal scaling
None
None
Multi-region
Read replicas
None
ACID
Limited
Full
Consistency
Strong
Strong
Schema
Schemaless
Strict
Architecture
Single node, Distributed, Client server
Single node, Primary replica, Client server
deployment
Self-hosted
✓
✓
Vendor-managed cloud
✓
—
Serverless
—
—
Embedded
—
—
Edge
—
—
Clouds
AWS, Google Cloud, Azure
AWS, Google Cloud, Azure
capabilities
Transactions
✓
✓
Joins
—
—
Secondary indexes
—
—
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
✓
✓
Change data capture
✓
—
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
—
Pub/Sub
✓
—
Columnar storage
—
—
In-memory
—
—
Durable persistence
✓
✓
Compression
—
—
Encryption at rest
✓
—
Role-based access
✓
—
Time travel
✓
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
✓
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
Stream reads/subscriptions API, JavaScript projections, SQL (Arrow Flight)
SQL
Client languages
C#, Java, JavaScript, Go, Python, Rust
Python, Rust, JavaScript, Go, Java, C#, Elixir
Best for
Event sourcing, OLTP, Pub/Sub, Streaming
Queue
Add more to this comparisonNot sure either fits? Try smart match

KurrentDB (EventStoreDB) vs PGMQ: FAQ

What is the difference between KurrentDB (EventStoreDB) and PGMQ?

KurrentDB (EventStoreDB): A purpose-built event store for event sourcing, with streams, subscriptions and projections. PGMQ: An SQS-style message queue implemented as a lightweight Postgres extension. KurrentDB (EventStoreDB) is primarily an event store database; PGMQ is relational. Licensing: KurrentDB (EventStoreDB) is source-available (Kurrent License v1 (KLv1)); PGMQ is open source (permissive) (PostgreSQL License). KurrentDB (EventStoreDB) is built for larger datasets (≤ 10 TB) than PGMQ (≤ 100 GB).

When should I choose KurrentDB (EventStoreDB) over PGMQ?

Choose KurrentDB (EventStoreDB) for event-sourced domain models with CQRS; audit-heavy financial and logistics systems; and integrating microservices via durable event streams. Choose PGMQ for background job queues for Postgres-backed apps, outbox pattern without a separate broker and lightweight task queues on Supabase.

Is KurrentDB (EventStoreDB) or PGMQ more popular?

PGMQ ranks #145 on the WhichDB Score (21.1/100) and KurrentDB (EventStoreDB) ranks #177 (18.6/100). Popularity is not fit: check the requirements that matter for your project.

Are KurrentDB (EventStoreDB) and PGMQ open source?

Not in the OSI sense. KurrentDB (EventStoreDB) is source-available: you can read the code, but the license restricts some uses, typically offering it as a competing managed service. License: Kurrent License v1 (KLv1). Yes. PGMQ is open source. License: PostgreSQL License.