Hi guys, in this lesson we will talk about what microservices are, and how it is different from monolithic applications. You know that normally we work just one project. And this project contains a database, a client side user interface, and the server side application. You know that a database consisting of many tables, usually in a relational database management system, you know that a client side consistent of HTML page and JavaScript running in a browser, you know, that as server side contains a lot of services like MVC model control. Also, all dependencies can be formed on just one configuration file. Actually, this is exactly what monolithic application is.

A monolithic application is built as a single unit. So all in one project, enterprise applications can be example for it. To understand exactly what micro services are, and why micro services, we should know the problems about normal ways. You know that in big projects, there are lots of developers and they push all of code into one single project. At the end of it, your big project will be bigger project day by day. So what can be problem with this big projects or bigger projects?

First one is, for example, you have a million lines of code in your project. If you has, if you have a problem with one line of them, the anti system does not work. Secondly, you You know, sometimes you need upgrade version of a library in your project. In that case, it will require the whole application to be upgraded, tested and deployed, because all modules are dependent to each other. Third one is if you work with continuous integration pipeline, you should deploy and test all system shortly in normal ways, you work with just one database and all relations are kept with a single scheme. These are the problems about monolithic application.

Now we can talk about micro services. micro services are to socialize big projects, two very small projects, interrupt in traditional monolithic application, there is simple module. But in microservices, there are different modules. Each of them has own model, own database and all dependencies. Micro service is not a project. It is project of projects, you know that in a project, ton of people can work and they are putting all of God into one single project.

So, you slice these kind of projects to very small projects, then you make them work together effectively. Let's talk about microservices advantages and disadvantages. micro services are suitable for big projects. So if you work with small project, monolithic application will be effective. If there is no reason for you to slice up something this small into microservices, you will just introduce a lot of complexity. With microservices, you can use different technologies and you can use different database schemas, because you have different modules.

Continuous integration and continuous development pipelines tabs can be handled easily and effectively with microservices, because you have small projects and these projects can be deployed easily. Third one is if you have an error on codebook, it does not affect all system. It will be just related with each service. The other one is, you know that scalability of a system is its capability to handle and Decreasing level of work. With microservices services can be scaled in the event independently. You can handle load balancing easily.

Actually, that's all about micro services. Thank you.