Overview

This guide provides an overview of the available client SDKs for EventSourcingDB. These SDKs make it easier to build applications that write, read, and observe events without having to interact with the HTTP API directly.

Each SDK is published and maintained independently, with its own documentation and release cycle. This page provides a central index of all known SDKs, grouped by origin and level of support.

Scope and Focus

Client SDKs are primarily designed to support application development. They focus on the core use cases of writing, reading, and observing events – operations typically required by business logic and services.

Operational or administrative features such as backup, restore, or monitoring endpoints are generally not included. While capabilities may vary between implementations, all SDKs are optimized for everyday development workflows rather than full API coverage.

Some SDKs also include support for running EventSourcingDB in a containerized test environment using Testcontainers. This is particularly useful for integration tests and automated test setups. Availability and implementation details vary by SDK.

Official SDKs

These SDKs are developed and maintained by the native web GmbH, the creators of EventSourcingDB. They receive regular updates and reflect the current state of the platform.

• .NET SDK
• Elixir SDK
• Go SDK
• Java SDK
• JavaScript SDK
• PHP SDK
• Python SDK
• Rust SDK

Community SDKs

These SDKs are developed independently by members of the community, outside of the official projects, but they contribute to the ecosystem and help make EventSourcingDB more broadly accessible.

We warmly welcome community contributions and are happy to list SDKs that are actively maintained and publicly available. If you've built one – or if you've spotted an SDK that seems outdated or broken – please get in touch at hello@thenativeweb.io. That helps us keep this list useful and reliable for everyone.

Compliance Criteria

For a detailed list of functional requirements that SDKs are expected to fulfill, see the Compliance Criteria. This checklist is used for internal reviews and serves as guidance for third-party developers.