- Go
- NATS, NATS JetStream, NATS Micro
- gRPC
- CockroachDB
- Go kit
- Zipkin (for distributed tracing)
Run the command below from the eventstream directory:
protoc eventstore/*.proto \
--go_out=. \
--go-grpc_out=. \
--go_opt=paths=source_relative \
--go-grpc_opt=paths=source_relative \
--proto_path=.
cockroach start \
--insecure \
--store=orders-1 \
--listen-addr=localhost:26257 \
--http-addr=localhost:8080 \
--join=localhost:26257,localhost:26258,localhost:26259 \
--background
cockroach start \
--insecure \
--store=orders-2 \
--listen-addr=localhost:26258 \
--http-addr=localhost:8081 \
--join=localhost:26257,localhost:26258,localhost:26259 \
--background
cockroach start \
--insecure \
--store=orders-3 \
--listen-addr=localhost:26259 \
--http-addr=localhost:8082 \
--join=localhost:26257,localhost:26258,localhost:26259 \
--background
cockroach init --insecure --host=localhost:26257
cockroach sql --insecure --host=localhost:26257
cockroach user set shijuvar --insecure
cockroach sql --insecure -e 'CREATE DATABASE eventstoredb'
cockroach sql --insecure -e 'CREATE DATABASE ordersdb'
cockroach sql --insecure -e 'GRANT ALL ON DATABASE ordersdb TO shijuvar'
cockroach sql --insecure -e 'GRANT ALL ON DATABASE eventstoredb TO shijuvar'
nats-server -js
nats-server -c js.conf
// js.conf file
jetstream {
// jetstream data will be in /data/jetstream-server/jetstream
store_dir: "/data/jetstream-server"
// 1GB
max_memory_store: 1073741824
// 10GB
max_file_store: 10737418240
}
http_port: 8222
- Run the NATS JetStream Server
- Run CockroachDB
- Run bootstrapper app (eventstream/bootstrapper) as a one time activity for creating stream in JetStream and create two databases in CockroachDB
- In order to use distributed tracing with gokit-ordersvc (order service with Go kit), run Zipkin distributed tracing system
- A client app post an Order to an HTTP API (ordersvc)
- An HTTP API (ordersvc) receives the order, then executes a command onto Event Store, which is an immutable log of events of domain events, to create an event via its gRPC API (eventstoresvc).
- The Event Store API executes the command and then publishes an event "ORDERS.created" to NATS JetStream server to let other services know that a domain event is created.
- The Payment worker (paymentworker) subscribes the event "ORDERS.created", then make the payment, and then create another event "ORDERS.paymentdebited" via Event Store API.
- The Event Store API executes a command onto Event Store to create an event "ORDERS.paymentdebited" and publishes an event to NATS JetStream server to let other services know that the payment has been debited.
- The Query synchronising worker (querymodelworker) subscribes the event "ORDERS.created" that synchronise the query data model to provide state of the aggregates for query views.
- The review worker (reviewworker) subscribes the event "ORDERS.paymentdebited" and finally approves the order, and then create another event "ORDERS.approved" via Event Store API.
- A Saga coordinator manages the distributed transactions and makes void transactions on failures (to be implemented)
As a Consulting Solutions Architect, I do provide training and consulting on Go programming language and distributed systems architectures, in India.