We could not find what you were looking for.
Please contact the owner of the site that linked you to the original URL and let them know their link is broken.
Booster is an open-source minimalistic TypeScript framework to build event-sourced services with the minimal amount of code possible, but don't let its innocent appearance fool you; Booster analyzes the semantics of your code, sets up theoptimal infrastructure to run your application at scale, and even generates a fully-working GraphQL API for you – don't even mind about writing the resolvers or maintaining your GraphQL schema, it will do that for you too.
And have we mentioned it's all open-source and free? But not free like you have a few build minutes per month or anything like that, we mean, real free. Everything remains between you, your CI/CD scripts (wherever you want to put them), and your own cloud accounts. Nothing is hidden under the carpet, you can visit the Github repository and see every single detail.
Despite you can place commands, and other Booster files, in any directory, we strongly recommend you to put them in <project-root>/src/commands. Having all the commands in one place will help you to understand your application's capabilities at a glance.
<project-root>
├── src
│ ├── commands <------ put them here
│ ├── common
│ ├── config
│ ├── entities
│ ├── events
│ ├── index.ts
│ └── read-models
<project-root>
├── src
│ ├── commands <------ put them here
│ ├── common
│ ├── config
│ ├── entities
│ ├── events
│ ├── index.ts
│ └── read-models
Entities live within the entities directory of the project source: <project-root>/src/entities.
<project-root>
├── src
│ ├── commands
│ ├── common
│ ├── config
│ ├── entities <------ put them here
│ ├── events
│ ├── index.ts
│ └── read-models
<project-root>
├── src
│ ├── commands
│ ├── common
│ ├── config
│ ├── entities <------ put them here
│ ├── events
│ ├── index.ts
│ └── read-models
Booster applications are event-driven and event-sourced so, the source of truth is the whole history of events. When a client submits a command, Booster wakes up and handles it throght Command Handlers. As part of the process, some Events may be registered as needed.
On the other side, the framework caches the current state by automatically reducing all the registered events into Entities. You can also react to events via Event Handlers, triggering side effect actions to certain events. Finally, Entities are not directly exposed, they are transformed or projected into ReadModels, which are exposed to the public.
In this chapter you'll walk through these concepts in detail.
-Commands are any action a user performs on your application. For example, RemoveItemFromCart, RatePhoto or AddCommentToPost. They express the intention of an user, and they are the main interaction mechanism of your application. They are a similar to the concept of a request on a REST API. Command issuers can also send data on a command as parameters.
An event is a fact of something that has happened in your application. Every action that takes place on your application should be stored as an event. They are stored in a single collection, forming a set of immutable records of facts that contain the whole story of your application. This collection of events is commonly known as the Event Store.
Learn how to react to events and trigger side effects in Booster by defining event handlers.
If events are the source of truth of your application, entities are the current state of your application. For example, if you have an application that allows users to create bank accounts, the events would be something like AccountCreated, MoneyDeposited, MoneyWithdrawn, etc. But the entities would be the BankAccount themselves, with the current balance, owner, etc.
A read model contains the data of your application that is exposed to the client through the GraphQL API. It's a projection of one or more entities, so you dont have to directly expose them to the client. Booster generates the GraphQL queries that allow you to fetch your read models.
Documentation for defining notifications in the Booster Framework using the @Notification and @partitionKey decorators.
ReadModels offer read operations over reduced events. On the other hand, Queries provide a way to do custom read operations.
Commands are any action a user performs on your application. For example, RemoveItemFromCart, RatePhoto or AddCommentToPost. They express the intention of an user, and they are the main interaction mechanism of your application. They are a similar to the concept of a request on a REST API. Command issuers can also send data on a command as parameters.
An event is a fact of something that has happened in your application. Every action that takes place on your application should be stored as an event. They are stored in a single collection, forming a set of immutable records of facts that contain the whole story of your application. This collection of events is commonly known as the Event Store.
Learn how to react to events and trigger side effects in Booster by defining event handlers.
If events are the source of truth of your application, entities are the current state of your application. For example, if you have an application that allows users to create bank accounts, the events would be something like AccountCreated, MoneyDeposited, MoneyWithdrawn, etc. But the entities would be the BankAccount themselves, with the current balance, owner, etc.
A read model contains the data of your application that is exposed to the client through the GraphQL API. It's a projection of one or more entities, so you dont have to directly expose them to the client. Booster generates the GraphQL queries that allow you to fetch your read models.
Documentation for defining notifications in the Booster Framework using the @Notification and @partitionKey decorators.
ReadModels offer read operations over reduced events. On the other hand, Queries provide a way to do custom read operations.