As we discussed the CQRS architecture is made out of two distinct service handlers, the command handler, and the query handler. Although they have different functionality, they still have the same execution

After the last blog post we are prepared to start the implementation of architecture aspects. First, we need to create a new project where we will place the aspects. We don't want to place them in an

This is a part of a series of blog posts about design and architecture patterns. Disclaimer! This blog post will only cover the theory of what every software architecture needs to provide in order to be

Today we start the last of design patterns (in the end !!!), which is called Strategy at reading of this article before someone reaches the bottom of the article to the section "relations with other

Today, about a fairly simple pattern called State, which serves to the very simple operation, as the name says to change the behavior of the object, when its internal state changes, i.e. when some event

Today, the pattern a little more complicated than the previous one, ie the Command pattern, is very similar to the Chain of Responsibility pattern, however, it differs a little, has a very similar purpose

We are starting another design pattern today, it is called Memento, it is a very simple to understand pattern, also the main picture of this article also translates the pattern, at the same time very

We are taking care of another design pattern, and it is Visitor, now entries can be irregular, I have some responsibilities, but a series of design patterns I want to finish :) We go with the theme :)

Hello again!! We are taking care of another design pattern, which in my opinion must be known compulsorily 🙂. And it is an observer pattern. Discussion The main purpose of this pattern is for example

Hello everyone!! After few months, I’m again! 😃😎🙂 I had a lot of others activities. Today is about the template method design pattern. Is a lot of to describe but about this is further in the post.

Today it was supposed to be about an operational pattern called Mediator, which satisfies the last SOLID principle, namely avoiding dependencies between classes, here we create one class that can be said

Today will be the theme, as I promised in the previous article, about the design pattern called a chain of obligations, also known as the chain of responsibility, it is perfect for assigning responsibilities

Now I will discuss the Iterator pattern, as the name suggests, it is used to iterate through collections, objects, etc. This is, in a nutshell, more precisely described in the article. Intent Providing

I am just as I promised after two weeks and as I promised I will be describing the interpreter design pattern, as you can guess it interprets some content on the content we want, ie it is used in translators

It’s time for another pattern, and more precisely for the Flyweight pattern, whose purpose is, in a nutshell, to limit the memory occupied by many objects, further on the article about the pattern. Intent

The proxy pattern is quite similar to the Bridge pattern, but the purpose of the Proxy is different, its purpose is to create an object that will represent another object, so in a nutshell, more precisely

Hello everyone! Today topic is about the Bridge design pattern however, we will change some form of the entry into a more structured one, so let’s get to the topic 🙂 Intent Separates abstractions from

Hi, I’ve recently found an interesting design pattern called Composite, which is used to fold objects into a tree structure, thanks to which the client sees instead of many objects only one. And that’s

In this article about the Facade design pattern , whose main task is to make the complex system available to the customer in the form of a simplified, ordered programming interface. Description and

Today, we will be talk about two design patterns, both are similar to the last solid principle, dependency inversion, in the sense that both are about the same problem, namely creating an instance of an