Common Code for Microservices. Hello, my friends. In this lesson, I want to talk about Common Code or in other words, shared libraries in Microservices. To get a good understanding, let's start with the monolith paradigm. When you create a monolithic application, you probably have some common policies in code libraries for some parts, such as logging, error handling, and monitoring. As a result, when clients use your application, they see the same notification at a specific workflow step or the same error message  if they engage in a certain incorrect behavior. 

Let's assume you've decided to migrate your application to a Microservices architecture. Microservice architecture, you see, requires us to atomize services. So, what are we going to do about the common parts of the application code? Should we use the same error codes for all services? If we did that, that means code duplication, which takes a significant amount of time and effort. So, instead, we can define some services for shared codes and other services can use those services to obtain Common Code specifications for required operations, such as logging, error handling and so on. All right.  So, let's take a short break here my friends, and I'll see you in the next lesson.