First, it's good to briefly talk about cloud-native. The term cloud-native, of course, includes the keyword cloud, so one might think about what technical elements should be used in cloud services, such as cloud-native. The CNCF, a well-known organization, has defined it. Of course, not everything defined by the organization is created as if it were the truth, but it is still one of the most influential organizations. In defining cloud-native, they present technical elements from four major aspects: architecture, development, infrastructure, and operations. On the architectural side, they talk about MSA, which stands for Microservices Architecture. On the development side, they discuss things like open APIs. In terms of infrastructure, it involves building with containers.

I am speaking. There are two aspects to the operational side, CCD and Death. By having these technological elements, we define them as cloud-native. To elaborate, CNCF is one of the most influential organizations in the cloud. When talking about cloud-native, it refers to applications that are scalable in a cloud environment, utilizing microservices architecture and declarative APIs. Loose coupling means communication should be done asynchronously, not only through API calls but also by having intermediaries. This is similar to implementing MSA. Engineers aim for minimal intervention in operations, hence discussing CI/CD. This was the context of discussing the composition of cloud-native.

When you organize the elements once, microservices architecture takes the center in the context of a more cloud-native approach to using the cloud. It involves reducing the size of application units and then these reduced units are carried in containers. Containers are a lightweight virtualization technology that achieves lightweighting by eliminating the need for guests. When these containers are loaded with applications, they can be deployed, which is what containerization is about. Furthermore, in terms of automating operations, there are DevOps and CI/CD. So, what is microservices architecture? This is also a definition of microservices architecture from a similar perspective, but there are some deployment specifics. Once you understand this, you can understand microservices architecture.

How are you defining and trying to create this, even though it's not a completely old-fashioned perspective, you can architect these elements and by understanding this architecture, you can better understand what microservices architecture is. Overall, this inside now corresponds to the architecture, and if you look at the entry point once, there can be mobile apps, browser apps, and other services. So, if you think of this situation as being called by these services, the call is made through communication. When the call is made here, it is structured to call API endpoints initially. So, when the API is called, it is configured to have an endpoint address. So, if there are services in the back end of this entire service, you can think of this as playing the role of the interface of this service. And typically, the API gateway plays this role.

A gateway will be one of the quite important components in configuring this kind of MSA. So, through the API gateway, services behind it are actually called. These services can have a large number of services inside, and there are various reasons for not exposing these services to the outside world. One of the main reasons is that directly exposing the addresses of these services to the outside world is not a good form of architecture. Another reason is that if the interfaces of these services change frequently internally, when making calls from apps or browsers, new development needs to be done differently. Therefore, by mostly making calls through a single interface, the role of reducing the impact of changes can be achieved. And, in the API gateway, these are the first of the overall API calls.

By taking on the role of the first entry stage, there are common tasks that need to be done, especially now as we express it in terms of Spectrum in ideology. In AOP, in such aspects, roles like authentication, etc., can also be done at the API Gateway. The API Gateway filters and processes overall API tasks, and then delegates the processing to API 2. Rules are established in API 2, and when an API is called, it goes through the basic steps of load balancing and service routing. Service routing means finding the service, while load balancing means distributing the traffic. In other words, it needs to locate where the service is and be able to make the call, and this role is carried out by service discovery. Discovery means that services are registered in advance in the service discovery, and once they are registered, the service discovery can be likened to.

When you call a service like DNS, just as you call an address, you look for a service through service discovery, and then you return the corresponding physical location to actually make the call. Therefore, one of the reasons for using service discovery is that microservices consist of many services to make up the entire service. Services can change locations at any time, expand services, add services BC or CD, and be flexible in this way. That's why connections are made by registering and finding services, rather than fixing them in place. And when you find it like that, instead of calling directly to the server, you go through load balancing. You can have two servers or three servers with the same server, or you can have more servers as needed. Instead of specifying each one, you use a load balancer at the front end to distribute traffic.

By using Doom, it helps to properly distribute this traffic, and that's how the entry is made. Inside, if you see it as instances, think of it as servers. This is now referred to as an inner architecture. This part is called inner architecture because it now applies to the software aspect. Outside, of course, most devices are also made up of software, but this now corresponds to the outer architecture, which is the part that constitutes the actual physical architecture. So, if applications are now entering here one by one, here you can see the config server, which is expressed as a config store. There is a config server. What is this config server? These instances place their configurations outside. Configuration.

Setting them externally makes management easier, and another thing is, this is called human error. For example, you might forget a setting that should have been made somewhere, so it's possible to forget. That's why managing separately from one place, the configuration server, and reflecting it in the application through one setting is how it's distinguished. Distinguishing between the application and settings is important. Another important thing is that these applications take various forms in development, staging, and operation. When these applications are developed, staged, and operated, the sources should be the same when dividing them into groups such as development and production. Then, what changes? It's the environment settings that change. Depending on the environment settings, here, a server can be one, two here, three here, or more than that, not only the number but also the location and who connects here.

Could the database change as well? Looking at the database, there are settings such as whether to look at the development database or the operational database. By setting those aspects here and making settings all at once, it reduces the impact of changes and facilitates provisioning. It is a concept of creating another server group to work very conveniently when creating one.

클라우드 네이티브 중 MSA 마이크로서비스 아키텍처

안녕하세요. 기술노트 채널을 운영하고 있는 알렉이라고 합니다. 

IT분야에 개발자로 일을 하다가 프로젝트 매니저로 현재는 IT컨설턴트로 일하고 있습니다. 
기술사 자격증 취득 관련 그리고 IT전반에 걸친 경험이나 지식을 올리고 있습니다. 

클라우드 강의 
https://inf.run/q1ia

백엔드 직접 번역한 추천 도서 
https://www.yes24.com/Product/Goods/122536127

앱개발을 해본 경험이나 방법들도 올렸습니다. 
앱개발 관련해서는 아래 링크 통해서 인프런에 무료로 올린 강좌 리스트를 참고하시구요. 
https://inf.run/4Ug3

기술노트 (클라우드, 빅데이터, 취업, 진로 고민등) 아래 링크 통해서 영상 참고해보시면 좋습니다. 
https://inf.run/x4mm

좋은 인연이 되었으면 좋겠습니다.

혹시 IT 분야 진로 관련 고민이나 빅데이터,
앱개발, 기술사 공부 관련 문의 주실게 있다면 
hitouchsoft@gmail.com 자유롭게 문의 주세요.

도움이 되셨다면 구독, 좋아요 눌러주시면 
영상 제작에 큰 힘이 됩니다~! 


클라우드 네이티브 중 MSA 마이크로서비스 아키텍처

클라우드 네이티브 중 MSA 마이크로서비스 아키텍처

스크립트