An Hexagonal Architecture with DDD + Aggregates + Event Sourcing using .NET Core, Kafka e MongoDB (Blog Engine)
Clone or download
Latest commit 15ac2de Mar 23, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
setup Spliting projects Dec 21, 2017
source Unit Tests Jan 25, 2018
.gitattributes OK Nov 3, 2016
.gitignore Initial commit Nov 1, 2016
CODE_OF_CONDUCT.md Código de conduta Sep 6, 2017
CONTRIBUTING.md guide Sep 6, 2017
LICENSE Initial commit Nov 1, 2016
Producer.png Spliting projects Dec 21, 2017
README.md docs Mar 23, 2018
_config.yml Set theme jekyll-theme-cayman Dec 22, 2017

README.md

A solution based on a Event-Driven architecture with DDD and CQRS. The solution contains the following applications.

  • A Producer Web API which receives Commands to produce Domain Events. This one also receives Queries and returns JSON.
  • A Consumer Console App that reads the Event Stream and do a projection to a MongoDB database.
  • A Web API for authentication and JWT generation.

Checkout the Source Code on GitHub

Requirements

Environment setup

If you already have valid connections for Kafka and MongoDB you could skip this step and go to Running the applications step.

  • Run the ./up-kafka-mongodb.sh bash script to run Kafka and MongoDB as Docker Containers. Please wait until the ~800mb download to be complete.
$ ./up-kafka-mongodb.sh
Pulling mongodb (mongo:latest)...
latest: Pulling from library/mongo
Digest: sha256:2c55bcc870c269771aeade05fc3dd3657800540e0a48755876a1dc70db1e76d9
Status: Downloaded newer image for mongo:latest
Pulling kafka (spotify/kafka:latest)...
latest: Pulling from spotify/kafka
Digest: sha256:cf8f8f760b48a07fb99df24fab8201ec8b647634751e842b67103a25a388981b
Status: Downloaded newer image for spotify/kafka:latest
Creating setup_mongodb_1 ...
Creating setup_kafka_1 ...
Creating setup_mongodb_1
Creating setup_mongodb_1 ... done
  • Check if the data layer is ready with the following commands:
$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
mongo               latest              d22888af0ce0        17 hours ago        361MB
spotify/kafka       latest              a9e0a5b8b15e        11 months ago       443MB
$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                            NAMES
32452776153f        spotify/kafka       "supervisord -n"         2 days ago          Up 2 days           0.0.0.0:2181->2181/tcp, 0.0.0.0:9092->9092/tcp   setup_kafka_1
ba28cf144478        mongo               "docker-entrypoint..."   2 days ago          Up 2 days           0.0.0.0:27017->27017/tcp                         setup_mongodb_1

If Kafka is running well it will be working with the 10.0.75.1:9092 connection string. if MongoDB is running well it will be working at mongodb://10.0.75.1:27017 connection string.

Running the applications

You have two options to run the applications, one is by opening with Visual Studio 2017 and the other is by running dotnet core commands.

Option 1 - Running with Visual Studio 2017

Open the three solutions on three Visual Studios them run the following projects.

  • Jambo.Auth.UI.
  • Jambo.Consumer.UI.
  • Jambo.Producer.UI.

Option 2 - Running with dotnet commands

How to run the Bearer Authencation API

  1. Run the command dotnet run at source\Auth\Jambo.Auth.UI folder.
$ dotnet run
Using launch settings from C:\git\jambo\source\Auth\Jambo.Auth.UI\Properties\launchSettings.json...
Hosting environment: Development
Content root path: C:\git\jambo\source\Auth\Jambo.Auth.UI
Now listening on: http://localhost:16024
Application started. Press Ctrl+C to shut down.
  1. Navigate to the Swagger UI at (eg. http://localhost:16024/swagger).
  2. Post the following credentials:
{
  "username": "ivanpaulovich",
  "password": "mysecret"
}
  1. Store the Bearer Token because you will need the token value to log on Producer API.
{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJqdGkiOiJhYzA4MmE3OS1lMWY3LTQ4MTktYmU1Mi1hOTQwMTBkM2VjZTciLCJzdWIiOiJzdHJpbmciLCJleHAiOjE1MTI0Nzg5ODgsImlzcyI6Imh0dHA6Ly9teWFjY291bnRhcGkiLCJhdWQiOiJodHRwOi8vbXlhY2NvdW50YXBpIn0.9YKGmKaptLBDcExHhPOQ3_j9TsdbkcRf8ZtvIkdq8Go",
  "expiration": "2017-12-05T13:03:08Z"
}

How to run the Consumer API

  1. Run the command dotnet run at source\Consumer\Jambo.Consumer.UI folder
$ dotnet run
11/5/2017 11:17:20 AM Waiting for events..
11/5/2017 11:18:20 AM Waiting for events..
11/5/2017 11:19:20 AM Waiting for events..
11/5/2017 11:20:20 AM Waiting for events..
11/5/2017 11:21:20 AM Waiting for events..
11/5/2017 11:22:20 AM Waiting for events..
  1. Attention: keep the Console App running for events processing.

How to run the Producer API

Authorization

  1. Run the command dotnet run at the source\Producer\Jambo.Producer.UI folder.
$ dotnet run
Using launch settings from C:\git\jambo\source\Producer\Jambo.Producer.UI\Properties\launchSettings.json...
Hosting environment: Development
Content root path: C:\git\jambo\source\Producer\Jambo.Producer.UI
Now listening on: http://localhost:16959
Application started. Press Ctrl+C to shut down.
  1. Navigate to the Swagger UI (eg. http://localhost:14398/swagger).