{"id":55323,"date":"2021-03-19T09:22:17","date_gmt":"2021-03-19T09:22:17","guid":{"rendered":"https:\/\/www.globallogic.com\/ua\/?post_type=insightsection&p=55323"},"modified":"2025-01-31T05:09:17","modified_gmt":"2025-01-31T05:09:17","slug":"microservices-architecture-for-beginners-part-one","status":"publish","type":"insightsection","link":"https:\/\/www.globallogic.com\/ua\/insights\/blogs\/microservices-architecture-for-beginners-part-one\/","title":{"rendered":"\u041c\u0456\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0456\u0441\u043d\u0430 \u0430\u0440\u0445\u0456\u0442\u0435\u043a\u0442\u0443\u0440\u0430 \u0434\u043b\u044f \u043f\u043e\u0447\u0430\u0442\u043a\u0456\u0432\u0446\u0456\u0432. \u0427\u0430\u0441\u0442\u0438\u043d\u0430 \u0406"},"content":{"rendered":"
\n
Author: Orkhan Gasimov, Technology Director, GlobalLogic<\/span><\/span><\/strong><\/h6>\n

Microservice architecture has been around for a while. However, there are many people looking for materials to get started and learn more about it. Despite the abundance of books and articles available, it is difficult to find a starting point for a quick start. Introductory material for the manager, engineer or architect, anyone. That is why I decided to write this article, in which I will list the basic principles and touch on the topics that you need to study if you want to gain a deep understanding of microservice architecture.<\/span><\/span><\/p>\n

What is a microservice?<\/span><\/span><\/span><\/h3>\n

A microservice is the simplest unit, a service that accepts incoming requests to perform an action. It can be a backend service that is available 24\/7 or a function that is called when an event occurs. In simple words, a function or set of functions available through a specific API over a network. So, this is a backend service deployed on a server. In a sense, it is a monolithic application. However, it does not carry the entire functionality of the system, but only a smaller part of the logic. Unlike a monolith, the resulting application is built as a set of relatively small independent services, called “microservices,” that communicate over a computer network. We can say that microservices are the same logical modules of a monolithic application that are distributed over a computer network, instead of working within a single process (device).<\/span><\/span><\/p>\n

\n

\"\"<\/p>\n<\/div>\n

A typical microservice web application reference architecture<\/span><\/span><\/em><\/p>\n

Microservices are usually structured in tiers. There are no rules as to how many or what tiers there should be, but there are best practices. The diagram above shows the most common tiers used in such architectures. The names may vary, but the structure is very similar to classic multi-tiered architecture. Logical tiers we see:<\/span><\/span><\/p>\n

Front-End \u2014 Client Application, Static Content <\/span><\/span>
\nBack-End \u2014 API Gateway, Experience Microservices, Domain Microservices <\/span><\/span>
\nData & Integration \u2014 Data Stores, Integration Interfaces \/ Connectors<\/span><\/span><\/p>\n

Let’s consider each tier and describe what it is responsible for.<\/span><\/span><\/p>\n

Logical tiers<\/span><\/span><\/span><\/h3>\n