A starter project for @node-ts/bus for building distributed message based systems with node.
@node-ts/bus is focused on helping build distributed systems in node based on messaging patterns that are reliable, scalable and fault tolerant. Applications built this way can:
- survive restarts and downtime
- handle bursty loads
- scale in and out easily
- survive network interruptions
- tolerate external API outages
- easily be refactored from monolith to microservice
All without losing data. This makes message based systems a great choice where reliability and data integrity is key.
However, building distributed message based applications isn't simple. At its heart, this project uses the service bus from @node-ts/bus that encapsulates many of the complexities when dealing with messaging technologies and approaches.
Your code stays cleaner, as only business logic related code needs to be written. Concerns on how a message is dispatched, routed, received, processed, retried etc are all handled by the underlying framework. This remains true regardless if the app operates in a single process in memory, or runs with many services and instances across many compute instances.
This starter project contains the following packages preconfigured and in a runnable state:
@node-ts/bus-core- The core service bus that manages sending, routing, dispatch, retries etc
This repository should be cloned or forked into your own repository:
git clone https://github.com/node-ts/bus-starter my-bus-app
cd my-bus-app
git remote set-url origin <your git repo>Then install the dependencies
npm iStart a local RabbitMQ container
docker run -d -p 8080:15672 -p 5672:5672 rabbitmq:3-managementRun the following command and observe the log output:
npm run devAt this point you can remove the existing messages/handlers/workflows and start implementing your own. Before moving to production, be sure to do the following tasks:
- configure a different transport
- install a durable persistence
These steps are crucial to ensuring your application is resilient and scalable
The following scripts are available as part of the starter project:
build- transpiles the code to/distdev- transpiles, runs and watches for code changeslint- runs linting based on @node-ts/code-standardslint:fix- attempts to fix linting violationstest- run all teststest:watch- run tests in watch mode
A small implementation of a distributed application has been made to demonstrate a generic project structure. This should be removed and replaced with your implementation.
The example used is testing sirens for correct operation (such as in a building fire alarm test). When a siren is tested, it publishes an event depending on success or failure. If a failure event is published, a workflow coordinates the sending of an email to the maintenance team to fix the siren.
This is a basic demonstration, but it shows how distributed systems can stay decoupled. By publishing an event that the siren is broken and orchestrating the remediation steps in a workflow, all commands of the system can adhere to the single responsibility principle and be reused without side effects.
For more information on how to use the service bus, visit @node-ts/bus.
If you're interested in Domain Driven Design to help design your code that reduces complexity, have a look at @node-ts/ddd which integrates seamlessly with the service bus.
The MIT License (MIT)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.