Architecture and Development
The public SDK surface is intentionally small: application code should primarily interact with client/.
Architecture Shape
At a high level:
client/exposes the public admin, table, config, row, and helper APIs- transport, codec, metadata, protobuf, and snapshot details stay under
internal/ - generated protobuf Go types are the internal protocol foundation
This lets the SDK stay Go-native at the API edge while still tracking the Fluss wire contract closely.
Current Implementation Priorities
The repo is currently investing most heavily in:
- writer hardening
- scanner ergonomics
- real-cluster coverage
- auth and observability gaps
For the full long-lived project memory, see:
Contributor Entry Points
If you want to work on the SDK itself:
- start with CONTRIBUTING.md
- use demo/fluss-dev for the fast local loop
- use demo/fluss-paimon when you need the broader real-cluster support contract