Flowly

Currently under development as an educational exercise, Flowly addresses the challenge of maintaining accurate, accessible documentation for event-driven systems where services communicate through asynchronous events rather than synchronous API calls, making system behavior harder to understand and debug. The planned features enable backward-compatible event design, potential TypeScript typing generation from schemas, automatic NPM package publishing for event contracts, and checking for unused event data fields that bloat payloads.

Perfect for microservices architectures using event-driven patterns, distributed systems teams maintaining event catalogs, organizations adopting domain-driven design with bounded contexts, or development teams where lack of event documentation leads to integration problems and duplicate event definitions. By centralizing event documentation with schema definitions, Flowly aims to create a single source of truth for event contracts across services, enabling teams to evolve systems confidently by understanding event dependencies, consumers, and schema compatibility before making breaking changes that could cascade through distributed architectures and cause production incidents.