At the moment, the service uses the command pattern to publish the command into the underneath layers. But we want to do the better one.

Reference at https://github.com/peasy/Peasy.NET/wiki and a sample at https://github.com/peasy/Samples

We have to review some of best practice on the internet like https://github.com/josdirksen/next-build-consul to make sure we do that right 🎱

Problem: At the moment, the config files put in many places in many projects, then it can make the config duplicated.
Solution: Need a way to central all config files into one place.

https://github.com/lecode-official/reactive-database-context
https://github.com/NickStrupat/EntityFramework.Triggers
https://github.com/NickStrupat/EntityFramework.Rx

Problem: All requests have to hit into the API gateway, then it will dispatch them into the correct one service, based on the url, e.g. https://localhost:8080/magazine/api/categories then it should forward to http://localhost:5000/api/categories
Solution: Have a look at http://josephwoodward.co.uk/2016/07/proxying-http-requests-asp-net-core-using-kestrel

At currently, the source code didn't build and publish correctly.
Reference at https://github.com/otsecbsol/sample-dotnetcore-microservices for how can we do that.

We have to separate entity configuration out to the DbContext at the moment.

Problem: At the moment, we use the DbContext for the ReadModel with the constraint on the specific entity. That looks like will not be a good approach for CQRS.
Solution: Apply the raw SQL execute, reference at http://www.elanderson.net/2016/04/execute-raw-sql-in-entity-framework-core, we can build 2 providers: SQL server and Postgresql.

Domain Object Backed By a State Object

Using ELK stack & host it in the Docker container. Reference at logging-with-logstash-elasticsearch-kibana-and-redis and the best one

At the moment, the code really messy and hard to read and maintain.

Reference at https://dzone.com/articles/23-useful-elasticsearch-example-queries

Actually, we need to cache the READMODEL like at RedisReadModelRepository.cs

[Obsolete]
Reference link at http://zablo.net/blog/post/asp-net-core-redis-html-cache

• Elm
• Webpack

Apply the elm-webpack-starter to speed up the development

Sample at https://github.com/HTBox/allReady
We have 2 reference resources at https://lostechies.com/jimmybogard/2015/05/05/cqrs-with-mediatr-and-automapper/ and http://stevejgordon.co.uk/cqrs-using-mediatr-asp-net-core

https://github.com/App-vNext/Polly

Dear Thang Chung,

Your application design is very good from a Microservice perspective ( dotnet core version). I am little confused on how and where the gateway is used. My understanding is Gateway is the one that will be exposed to your app/website and all microservices will be communicated using the gateway.

Please correct me if I am wrong.

One more question, if Magazine service wants to communicate with the sample service, how can this be achieved.

I am kind of new this concept of Microservices, so trying to understand.

Please help me understand, so that it can be helpful to someone who is willing to learn from your code base.

Thanks & Regards,
Raju

Hi Thang,

What is the development OS to run docker in this project? Are you using Docker for Windows, Docker Toolbox for Windows or Docker for Linux? The project is built and run at http://localhost:5000/ping

Thank you.
Khoa

The awesome article at Event Sourcing awesome and the sample code
Consider to apply it and use the project at eventstore-docker for the infrastructure.

References to myget at My packages

Like the Auth Service, we like the way that all the related components will keep into the same folder.

At the moment, we have a lot of common libs, but not actually publish for another people to use it.
Suggest the name for that lib should be Cik.CoreLibs 💯 .

Reference it at aws-blog-net-exploring-aspnet-core