From 5f25d083419d5565b4e4be31f99270c59958b8e6 Mon Sep 17 00:00:00 2001 From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com> Date: Fri, 17 Jun 2022 15:13:48 +0430 Subject: [PATCH 1/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 233b855..de00569 100644 --- a/README.md +++ b/README.md @@ -135,7 +135,7 @@ Run this app in docker using the [docker-compose.yaml](./deployments/docker-comp ```bash docker-compose -f ./deployments/docker-compose/docker-compose.yaml up -d ``` -Also we have a seprate docker file for up and running [infrastructure](./deployments/docker-compose/infrastracture.yaml) independently. +Also we have a seprate docker file for up and running [infrastracture.yaml](./deployments/docker-compose/infrastracture.yaml) independently. ```bash docker-compose -f ./deployments/docker-compose/infrastracture.yaml up -d From d08cc9e0e8bfbfc94f549a09d3fb8fab394b19fd Mon Sep 17 00:00:00 2001 From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com> Date: Fri, 17 Jun 2022 23:38:33 +0430 Subject: [PATCH 2/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index de00569..40b536d 100644 --- a/README.md +++ b/README.md @@ -135,7 +135,7 @@ Run this app in docker using the [docker-compose.yaml](./deployments/docker-comp ```bash docker-compose -f ./deployments/docker-compose/docker-compose.yaml up -d ``` -Also we have a seprate docker file for up and running [infrastracture.yaml](./deployments/docker-compose/infrastracture.yaml) independently. +Also we have a seprate docker file for up and running [infrastracture.yaml](./deployments/docker-compose/infrastracture.yaml) independently: ```bash docker-compose -f ./deployments/docker-compose/infrastracture.yaml up -d From 586e1798881bb9d78bf633426c2f6d109abdc067 Mon Sep 17 00:00:00 2001 From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com> Date: Sat, 18 Jun 2022 01:37:23 +0430 Subject: [PATCH 3/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f328fbe..4a85f70 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Booking Microservices is a Sample application for booking ticket. This applicati - Correct `separation of bounded contexts` for each microservice. - Communication between bounded contexts through asynchronous `MessageBus` and `events`. - Communication internally between our microservices with `gRPC` synchronously. -- Simple `CQRS` implementation and Event Driven Architecture with using SqlServer in write side and MongoDB in read side. I use an internal processor for syncing read side and write side without event sourcing. In booking microservice, I also use event store to store all historical state of aggregate. +- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for `syncing read side and write` side without event sourcing. In booking microservice, I also use `event store` to store all historical state of aggregate. - Using `Inbox Pattern` for guaranty message Idempotency for receiver microservice and `Exactly-once Delivery pattern` and using `Outbox Pattern` for ensuring about any message `lost and At-Least one Delivery` rule. - Implementing various types of testing like `Unit Testing`, `Integration Testing`. - Using `Health Check` for reporting the health of app infrastructure components. From d326b7c4b5ceed9c47991b6b129d545730ab97a7 Mon Sep 17 00:00:00 2001 From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com> Date: Sat, 18 Jun 2022 01:38:25 +0430 Subject: [PATCH 4/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4a85f70..2e6541d 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Booking Microservices is a Sample application for booking ticket. This applicati - Correct `separation of bounded contexts` for each microservice. - Communication between bounded contexts through asynchronous `MessageBus` and `events`. - Communication internally between our microservices with `gRPC` synchronously. -- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for `syncing read side and write` side without event sourcing. In booking microservice, I also use `event store` to store all historical state of aggregate. +- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for syncing `read side` and `write side` without event sourcing. In booking microservice, I also use `event store` to store all historical state of aggregate. - Using `Inbox Pattern` for guaranty message Idempotency for receiver microservice and `Exactly-once Delivery pattern` and using `Outbox Pattern` for ensuring about any message `lost and At-Least one Delivery` rule. - Implementing various types of testing like `Unit Testing`, `Integration Testing`. - Using `Health Check` for reporting the health of app infrastructure components. From 16a7f8cfe7e4ccd52e6807d636cce13ea0f7d865 Mon Sep 17 00:00:00 2001 From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com> Date: Wed, 22 Jun 2022 21:59:09 +0430 Subject: [PATCH 5/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2e6541d..d3e38e8 100644 --- a/README.md +++ b/README.md @@ -159,7 +159,7 @@ Thanks a bunch for supporting me! ## Contribution -Contributions are always welcome! Please take a look at the [contribution guidelines](https://github.com/meysamhadeli/booking-microservices-sample/blob/master/contributing.md) pages first. +Contributions are always welcome! Please take a look at the [contribution guidelines](https://github.com/meysamhadeli/booking-microservices-sample/blob/main/contributing.md) pages first. Thanks to all [contributors](https://github.com/meysamhadeli/booking-microservices-sample/graphs/contributors), you're awesome and this wouldn't be possible without you! The goal is to build a categorized community-driven collection of very well-known resources. From 0be5d7591ec218d58a1a1d9056cac0326d4b5494 Mon Sep 17 00:00:00 2001 From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com> Date: Wed, 22 Jun 2022 22:01:06 +0430 Subject: [PATCH 6/6] Update README.md --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d3e38e8..b539bf2 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,8 @@ Booking Microservices is a Sample application for booking ticket. This applicati - Correct `separation of bounded contexts` for each microservice. - Communication between bounded contexts through asynchronous `MessageBus` and `events`. - Communication internally between our microservices with `gRPC` synchronously. -- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for syncing `read side` and `write side` without event sourcing. In booking microservice, I also use `event store` to store all historical state of aggregate. +- Simple `CQRS` implementation and Event Driven Architecture with using `SqlServer` in `write side` and `MongoDB` in `read side`. I use an `internal processor` for syncing `read side` and `write side` without event sourcing. +- Using `event store` to store all historical state of aggregate. (Booking-Microservice) - Using `Inbox Pattern` for guaranty message Idempotency for receiver microservice and `Exactly-once Delivery pattern` and using `Outbox Pattern` for ensuring about any message `lost and At-Least one Delivery` rule. - Implementing various types of testing like `Unit Testing`, `Integration Testing`. - Using `Health Check` for reporting the health of app infrastructure components. @@ -159,8 +160,6 @@ Thanks a bunch for supporting me! ## Contribution -Contributions are always welcome! Please take a look at the [contribution guidelines](https://github.com/meysamhadeli/booking-microservices-sample/blob/main/contributing.md) pages first. - Thanks to all [contributors](https://github.com/meysamhadeli/booking-microservices-sample/graphs/contributors), you're awesome and this wouldn't be possible without you! The goal is to build a categorized community-driven collection of very well-known resources. ## Project References & Credits