Skip to content

Capability matrix

Which Pattern × Adapter combinations ship today, and which gaps the 1.0.0 milestone closes.

The roadmap and the milestones carry the live state. This page is the at-a-glance view.

Vocabulary

  • Pattern: user-facing class. Lock, LeaderElection, TaskLock, TTLCache, RateLimiter, CircuitBreaker, Retry, Bulkhead, Fallback.
  • Adapter: concrete implementation of a Backend Protocol. RedisSyncAdapter, PostgresSyncAdapter, MemoryCacheAdapter, SQLiteSyncAdapter, KubernetesSyncAdapter, and so on.
  • Backend: the Protocol class an Adapter satisfies. SyncBackend, CacheBackend, RateLimiterBackend, CircuitBreakerBackend.
  • Provider: vendor configuration plus native client, shared by Adapters that talk to the same service. RedisProvider, PostgresProvider. Memory, SQLite, and Kubernetes Adapters do not use a Provider.

See Backends and Adapters for the full model.

Matrix

Pattern Memory Redis Postgres SQLite Kubernetes
Lock ✅ ✅ ✅ ✅ ✅
TaskLock ✅ ✅ ✅ ✅ ✅
LeaderElection ✅ ✅ ✅ ✅ ✅
TTLCache ✅ ✅ #167 Future N/A
RateLimiter ✅ ✅ #164 #173 N/A
CircuitBreaker ✅ #163 Future Future N/A
Retry ✅ N/A N/A N/A N/A
Bulkhead #168 N/A N/A N/A N/A
Fallback #199 N/A N/A N/A N/A

Legend:

  • ✅ ships today.
  • #N planned for 1.0.0, tracked by the linked issue.
  • Future planned past 1.0.0.
  • N/A does not apply. Retry, Bulkhead, and Fallback are in-process Patterns with no remote state to share.

What 1.0.0 commits to

Closing every gap above that links to an issue. Anything marked Future is out of scope for 1.0.0.

Picking an Adapter

  • Memory for tests, single-process apps, and Retry (the only in-process Pattern that ships today). Bulkhead and Fallback will join this group at 1.0.0.
  • Redis when you already run Redis and want the lowest-latency distributed option.
  • Postgres when Postgres is your only stateful dependency and you want one fewer service to run.
  • SQLite for single-host deployments that still need durability across restarts.
  • Kubernetes for Lock and LeaderElection when you want the cluster API as the coordination plane and no extra infrastructure.