Skip to content
WeftKitBeta
Ecosystem

Beyond Databases.
The Full Ecosystem.

Six specialized infrastructure images that transform individual engine containers into a complete distributed data platform — CDC, replication, discovery, persistence, gateway, and a million-connection proxy.

Six Components

Infrastructure for Production

Each ecosystem component is independently deployable and composable with any combination of database modules.

cdc

CDC

Capture every mutation. Emit to any destination.

WAL-subscription-based change capture that emits structured events to queues, webhooks, files, or custom consumers. Over 100K events/sec throughput.

  • 4 emitter types (queue, webhook, file, custom)
  • > 100K change events/sec
  • Dead letter queue for failed deliveries
  • Resume tokens for at-least-once delivery
  • Schema filtering and event transformation
  • Compatible with all 8 database modules
Learn more
distribution

Distribution

Raft consensus. Same-type replication. Configurable consistency.

Multi-instance data replication using Raft consensus. Supports eventual and strong consistency with quorum writes, anti-entropy repair, and automatic failover.

  • Raft consensus protocol
  • Eventual + Strong consistency modes
  • Quorum writes (configurable)
  • Anti-entropy repair
  • Same-type replication only
  • Requires Discovery component
Learn more
discovery

Discovery

Know your cluster. Track health. Manage groups.

Lightweight service registry for WeftKit instances. SWIM-based membership protocol with heartbeat monitoring, group management, and health status tracking.

  • SWIM gossip membership protocol
  • Heartbeat health monitoring
  • Database group management
  • Automatic peer detection
  • mTLS secured registry
  • REST + gRPC management API
Learn more
persistence

Persistence

Local speed. Central durability.

Bridges embedded databases and central standalone servers. Supports write-through and write-behind modes with offline operation and automatic conflict resolution.

  • Write-through and write-behind modes
  • Offline operation with queue
  • LWW and CRDT conflict resolution
  • Configurable sync intervals
  • Bandwidth throttling
  • Requires Standalone instance
Learn more
standalone

Standalone

Standard wire protocols. Full server deployment.

Wraps any database module with a full network server supporting standard wire protocols. PostgreSQL, Redis RESP3, MongoDB Wire, Bolt, DynamoDB REST, and S3 REST.

  • PostgreSQL v3, Redis RESP3, MongoDB Wire
  • Bolt (Neo4j), DynamoDB REST, S3 REST
  • Dual-protocol server
  • TLS 1.3 mandatory
  • SCRAM-SHA-256 authentication
  • Full RBAC enforcement
Learn more
pool

Pool Manager

One million connections. Zero compromise.

io_uring-based connection proxy handling 1M+ concurrent connections with intelligent query routing, read/write splitting, connection multiplexing, and a built-in query cache.

  • io_uring async I/O (Linux)
  • 4 routing algorithms
  • Read/write splitting
  • Query result caching
  • < 1 μs connection acquisition
  • > 500K queries/sec proxy throughput
Learn more
Data Flow

How Components Connect

Ecosystem components interact through well-defined interfaces, composable at runtime without recompilation.

1
Database ModulesCDC

WAL events streamed as structured change events

2
CDCQueues / Webhooks

Events routed to any destination with at-least-once delivery

3
DiscoveryDistribution

Peer registry enables Raft-based consensus replication

4
Engine ImagePersistence

Write-through or write-behind sync between engine instances

5
StandalonePool Manager

Connection proxy with 1M+ concurrent connections

Runtime Dependencies

What Each Component Requires

Some components are fully standalone; others require companion services at runtime.

ComponentRequiredOptional
CDCStandalone — no dependenciesAny DB Module (WAL hook)
DistributionDiscoveryAny DB Module
DiscoveryStandalone — no dependencies
PersistenceStandalone instanceAny DB Module
StandaloneOne DB ModuleMultiple protocols
Pool ManagerStandalone instanceMultiple backends
Composable Configurations

Common Deployment Patterns

Mix and match ecosystem components for your specific use case.

Local-First Mobile

Medium

Per-tenant engine stack with cloud sync via Persistence layer

WeftKitRel/KVPersistenceStandalone

Event-Driven Microservices

Medium

Change events streamed to message queues for service coordination

WeftKitDoc/RelCDCStandalone

Multi-Region HA

High

Raft consensus replication across availability zones

Any DB ModuleDiscoveryDistributionStandalone

High-Throughput Proxy

Low

1M+ connections with read/write splitting and query caching

StandalonePool Manager

Full Platform

High

Complete enterprise deployment with all capabilities enabled

All 8 DB ModulesCDCDiscoveryDistributionPersistenceStandalonePool Manager

Ready to Build the Full Stack?

Combine database modules with ecosystem components to build a production-ready distributed data platform — every piece shipped as its own Docker image.