Spine Event Engine

Hi everyone! Alexander from Spine Event Engine here. We have built the Spine framework to help development groups like us to apply Domain-Driven Design easier. The books on DDD are great, but after you finish reading them, you end up with the question, “Now what?” And answering the question in the code takes a lot of time. So, we wanted to accumulate our experience and build a framework that would help us and people like us work with the focus on the business needs, rather than “plumbing” with infrastructure or “marrying” the variety of programming languages each modern cloud app requires. The framework helps and encourages applying Event-Driven Architecture, Event Sourcing, CQRS, Hexagonal Architecture, and more. The Spine framework is based on Google Protobuf, and we apply our code generation on top of it. A lot. It saves time and energy. In a big way. You define commands, events, states of entities, in Protobuf, along with Spine-specific validation attributes for your model. Then the Model Compiler generates the code for Java, JavaScript, and Dart. You can also generate API for other languages using the proto files and corresponding Protobuf Compiler (see: https://github.com/protocolbuffe...). Then you add business logic in Java, and repeat the process for each Bounded Context of your solution. The framework also provides a convenient API for arranging testing. Together with in-memory storages, it helps with testing a lot. We’d love your feedback and will be happy to answer your questions on getting your DDD projects started using our framework.