The sixth episode was released. During this video, we make use of Consul – a service registry, which enables the service discovery capabilities for the microservices and eventually, we add Fabio on top of the stack, which provides an additional load balancer and a dynamic routing table.
The fifth episode is available. In this video, we talk about queries (read side) part of CQRS. At first, we implement QueryHandlers and DTOs and eventually, we introduce an internal HTTP communication between API Gateway and microservice using RestEease.
The fourth episode was published. In this video, we’re implementing the events and event handlers as a way of asynchronous integration between microservices, that reduces the temporal coupling and improves the overall resiliency.
The third episode is available. We’re talking about the RabbitMQ message bus and implementing the message subscription on the service side, meaning that you shall be able to listen to the particular messages being sent to the message bus and handle them, just as we did in the previous episode, using in-memory command dispatcher.
The second episode is here. In this video, we’re going through CQRS and implement a basic HTTP API, that is able to receive and handle the command. In the next episodes, we’ll be extending the newly created Discounts Service, in order to make it work with the overall solution (remaining microservices).
Hi there, folks. It’s been a while (a quarter to be exact) since I’ve announced for the first time Microservices in .NET Core with DShop series as a part of DevMentors idea. I do apologize for not being consistent back then, however, there was a single reason for it – together with Darek we did rewrite lots of code after gathering a great feedback during our lectures.
May I present you, the very first teaser of our incoming video series.
In the previous post, being sort of a teaser, I made a brief introduction to DShop project, as well as the idea behind the overall course. Starting from now on, we’ll focus on the fundamental parts of DShop, including the theory behind a particular concept, its possible solutions, and eventually an implementation.
It’s been a while since I published the latest article, but it’s high time to finally get into the topic of microservices for real. Does open source, .NET Core, distributed system, Docker and other cool words sound good to you? If that’s the case, stick with me and let me guide you through the world (or at least part of it) of microservices. This is going to be the very first article (an introduction) of the upcoming series.
Recently I’ve been doing a lot of DevOps in order to automate the continuous integration and deployment (CI & CD) of the microservices as much as possible. In this article, I’d like to share with you some of my experiences how to get started with creating your own deployment process and this is going to be the first part of the series of articles related to this process.
Not so long ago, I’ve eventually decided to dive into the world of microservices.
I did look for an opportunity to make use of this architectural pattern for quite some time and finally was able to do so.
After 3 months of trying out the new things and learning stuff mostly on my own (the hard way) I believe it’s a good time to share some of my experience. I have no doubts that at some point in the future when I look back at this post I might be like – “oh God, what was I thinking back then, it’s so wrong”, but well, let me show you what did I learn so far and maybe you won’t repeat some of my mistakes.