gradyzhuo/swift-kurrentdb
This system is a Swift client library for the KurrentDB event sourcing platform, providing a comprehensive API for interacting with the database's v2 gRPC services. It enables developers to manage streams, persistent subscriptions, projections, and user accounts, while also offering administrative controls for cluster topology, node operations, and server monitoring. The library supports advanced features like multi-stream batch appends, configurable retry policies, and per-call authentication, all structured around a target-scoped, protocol-based architecture.
61.8
Adequate · 4 August 2026
43k
lines of production code
Swift
primary language
1
bus factor · 1 authors in all
3
measurements over time
How it got here
2023–2025 · KurrentDB client library rewrite
The codebase underwent a major architectural overhaul, renaming the project to KurrentDB and replacing the legacy EventStoreDB client with a new, protocol-based gRPC abstraction layer. This period focused on implementing comprehensive APIs for streams, persistent subscriptions, projections, and user management, supported by extensive new test coverage and cluster discovery features.
42 changes
2026 · KurrentDB v2 API and client expansion
This period focused on introducing the KurrentDB v2 API with new gRPC services for streams, schema registry, and system administration. The client library was expanded to support projections, user management, and cluster operations, while a V1 compatibility layer was added for backward compatibility. Additionally, local development environments and comprehensive test coverage were established to support the new features.
14 changes
Survey your own repository
gradyzhuo/swift-kurrentdb was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit df88f22667 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.