Spine Event Engine is a framework for building cloud applications based on Event-Driven Architecture and CQRS pattern.

We want to free developers from writing boilerplate code as much as possible. The primary language of the backend is Java. Client libraries are available for Java, JavaScript, and C++.

Libraries for client apps in Kotlin and Swift are in the priority list. We also plan to provide server-side API for Go and Node.js.

Features

Strongly Typed Domain Model

Spine promotes strong typing of all parts of a business model. You don't have to deal with Json.

Code Generation

The model is defined and maintained in Protobuf. The code is automatically generated for all the languages of your project, as you update the model.

Choice of Storage and Deployment Platforms

The framework promotes writing storage- and platform-agnostic code. You can start with JDBC and later switch to Google Cloud Platform Datastore by changing few lines of code.

Model Extensibility

Thanks to Protobuf support, a model can be extended preserving backward compatibility with clients running older code.

Promoted Immutability

Commands, events, query results, entity states, and other data are immutable. This makes them automatically thread-safe, and as such are freely shared or referenced.

Open Source

Permissive Apache License allows using the framework in closed-source projects. You are welcome to contribute to the framework development.

Built-in Validation

Constrains defined in a business model are automatically checked for commands, events, and entity states.

Multitenancy Support

Transforming a single-tenant application into a multi-tenant one requires very few lines of code. You don't have to introduce tenantId parameters for all the calls.

The story behind Spine

We started working on the framework after two CQRS/ES projects. Having the experience of tons of manual work for creating commands, events, message handlers, delivering messages and data to web and mobile clients, we thought that there must be a more productive.

Using existing CQRS/ES frameworks caused us to compromise on a number of things, including type safety, immutability, writing conversion code for inter-platform communications, etc. So in June 2015 we decided to build a tool for us and software developers like us.


Software that help us build Spine