The foundation is solid. Next up: multi-version schemas and replay tools.
Get it here: github.com/c0deZ3R0/go-sync-kit
What's your biggest offline-first pain point? We're planning v0.21.0 based on your feedback!
#golang #opensource #cqrs #offlinefirst #eventdriven
(3/3)

So what's new in v0.20.0?
✨ Production-ready projections with zero boilerplate
✨ BadgerDB integration (91.5% test coverage!)
✨ Full observability (Prometheus + structured logging)
✨ Battle-tested: thread safety, graceful shutdown & error recovery
It's built to work when the internet doesn't.
(2/3)

Still learning a ton about distributed systems! Check out the example code in the repo if you want to see it in action. A proper test suite is also in the works.
#opensource

The demo also features:
- Last-write-wins conflict resolution in action
- Real-time event propagation between clients

The SQLite storage + HTTP transport combo is working smoothly. Next up: more sophisticated conflict resolution strategies.

This is a "learning in public" project for me. I'm actively looking for feedback, contributors, and mentors. If you're interested in Go or distributed systems, please take a look, star, or open an issue! All contributions are welcome.
#distributedsystems #foss #learntocode
github.com/c0deZ3R0/go-...

The core idea is a clean, pluggable architecture. You can bring your own storage (SQLite included), transport (HTTP included), and conflict resolvers.
The latest release adds a VersionedStore decorator with a full vector clock implementation for handling concurrent writes in distributed systems.