Step 1.
Define rich, type‑safe domain model
Describe commands, events, and state of entities using Protobuf.
// A command to create a new task.
message CreateTask {
TaskId id = 1;
string name = 2 [(required) = true];
string description = 3;
}
...
// A new task has been created.
message TaskCreated {
TaskId id = 1;
string name = 2 [(required) = true];
string description = 3;
}
...
message Task {
(entity).kind = AGGREGATE;
TaskId id = 1;
string name = 2 [(required) = true];
string description = 3;
DeveloperId assignee = 4;
}Step 2.
Generate the code for all tiers and multiple languages
Java, JavaScript, and C++ are currently supported.
Step 3.
Code business logic in straight and testable way
Focus on business logic rather than “plumbing”.
A Command will be delivered to only one Aggregate.
Projections will get all Events they need.
ProcessManagers will cover more complex scenarios.
Storage, message delivery, and other environment matters are isolated from the main code.
final class TaskAggregate
extends Aggregate<TaskId, Task, Task.Builder> {
...
@Assign
TaskCreated handle(CreateTask cmd, CommandContext ctx) {
return TaskCreated
.newBuilder()
.setId(cmd.getId())
.setName(cmd.getName())
.setOwner(ctx.getActor())
.vBuild();
}
...
}
final class TaskProjection
extends Projection<TaskId, TaskItem, TaskItem.Builder> {
...
@Subscribe
void on(TaskCreated e) {
builder().setId(e.getId())
.setName(e.getName())
}
@Subscribe
void on(TaskCompleted e, EventContext ctx) {
builder().setWhenDone(ctx.getTimestamp());
}
}Step 4.
Easily deploy to Google Cloud or a custom environment
In-memory and JDBC-based storage implementations allow to implement and test the core logic quickly. Adopt your application to selected deployment environment(s) with a few lines of code.
Why Spine?
The code is automatically generated for all the languages of
your project, as you update the model.
Forget about missed hashCode() or equals().
Constraints defined in a business model are automatically checked for commands, events, and entity states.
With CQRS and Event-Driven Architecture you can separate development workflows. More experienced team members can concentrate on the core domain and the write-side tasks while the read–side and UI are created by the rest of the team.
Concepts from the DDD books, such as
Aggregate,
Projection,
ProcessManager,
Repository are right in the code.
Ever guessed how to cook a BoundedContext?
Guess no more!
Should you need CustomerId or
WorkEstimate value, you get it within seconds,
for multiple languages. You can also have binary storage format
and automatic JSON support.
Add and remove fields while keeping binary compatibility with older code;
handle new opportunities with oneof, natively provided by Protobuf.
Build new Projections based on the whole event history of the system.
All the data types are immutable, which makes it easy to cache and share. Mutations are performed only in response to incoming messages using clearly defined cycles.
The framework promotes development of storage- and platform-agnostic code. You can start with JDBC and later switch to Google Cloud Platform Datastore simply changing a few lines of code.
Use freely in closed-source projects. You are also welcome to contribute to improving our framework.