쉐도잉 연습: What Are Microservices Really All About? (And When Not To Use It) - 영상으로 영어 말하기 배우기

연습 모드 선택

각 모드는 전체 화면 연습실로 열립니다.

49 문장

문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.

Microservices architecture enables large teams to build scalable applications that are composed of many loosely coupled services.

What does a typical microservices architecture look like, and when should we use it?

Let's take a look.

Microservices are loosely coupled.

Each service handles a dedicated function inside a large-scale application.

For example, shopping cart, billing, user profile, push notifications can all be individual microservices.

These functional areas are sometimes called domains.

Microservices communicate with each other via well-defined interfaces with small service areas.

The small service areas limit the blast radius of failures and defects.

it makes each service easier to reason about in the context of the entire application.

Microservices talk to one another over a combination of remote procedure calls, or RPC, event streaming, or message brokers.

RPC like GRPC provides faster response,

but the blast radius or the impact to other microservices would be larger when the service was to go down.

Event streaming provides better isolation between services, but they take longer to process.

Microservices can be independently deployed.

Since each service is smaller, easier to reason about, and has a smaller blast radius.

This gives the operators peace of mind and confidence to deploy often.

Microservices provide more flexibility to scale up individual microservices independently.

The operational flexibility is invaluable.

Well-architected microservices practice strong information hiding.

This often means breaking up a monolithic database into its logical components

and keeping each logical component well hidden inside its corresponding microservice.

By logical component, it could mean a separate schema within a database cluster or an entirely separate physical database.

This is an implementation detail.

However, one big drawback of microservices is the breaking up of the database.

By breaking up a database into separate logical units,

the database can no longer maintain foreign key relationships and enforce referential integrity between these units.

The burden of maintaining data integrity is now moved into the application layer.

Now, let's take a look at other critical components required for a successful implementation of microservices architecture.

A key component is an API Gateway.

API Gateway handles incoming requests and routes them to the relevant microservices.

The API Gateway relies on an identity provider service to handle the authentication and authorization

of each request coming through the API Gateway.

To locate a service to route an incoming request to, the API Gateway consults a service registry and Discovery Service.

Microservices register with this service registry and discover the location of other microservices through the Discovery Service.

There are other useful components in a microservices architecture, like monitoring and alerting, DevOps toolings for deployment and troubleshooting, for example.

Let's wrap up by discussing when to use microservices architecture.

Microservices cost money to build and operate.

It really only makes sense for large teams.

For large teams, it enables team independence.

Each domain or function can be independently maintained by a dedicated team.

In a well-designed microservices architecture, these independent teams can move fast and the blast radius of failure is well-contained.

Each service could be independently designed, deployed, and scaled.

However, the overhead of a SANG implementation is so large that it is usually not a good fit for small startups.

One advice for startups is to design each function in the application with a well-defined interface.

One day, if the business and team are growing fast, that microservices architecture starts to make sense, it will be manageable to migrate.

If you would like to learn more about system design, check out our books and weekly newsletter.

Please subscribe if you learned something new.

Thank you so much and we'll see you next time.

앱 다운로드

유창하게 말하는 데 필요한 모든 것

AI 발음 평가문장마다 점수 확인

IPA 발음 연습모든 소리 마스터

단어 학습나만의 단어장 만들기

단어 게임놀면서 외우기

QR 스캔

Download on theApp Store Get it onGoogle Play

같은 채널

FOR YOU

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: What Are Microservices Really All About? (And When Not To Use It) - 영상으로 영어 말하기 배우기

연습 모드 선택

앱 다운로드

같은 채널

Top 5 Redis Use Cases

The Secret Sauce Behind NoSQL: LSM Tree

Proxy vs Reverse Proxy (Real-world Examples)

Cache Systems Every Developer Should Know

System Design Was HARD - Until You Knew the Trade-Offs

8 Most Important System Design Concepts You Should Know

Everything You Need to Know About DNS: Crash Course System Design #4

CAP Theorem Simplified

What Is REST API? Examples And How To Use It: Crash Course System Design #3

System Design: Why is Kafka Popular?

System Design: Why is Kafka fast?

What is API Gateway?

10+ Key Memory & Storage Systems: Crash Course System Design #5

What Is Redis Really About? Why Is It So Popular?

Kubernetes Explained in 6 Minutes | k8s Architecture

How Does a URL Shortener Work?

How Git Works: Explained in 4 Minutes

추천 영상

Microservices explained - the What, Why and How?

Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table

What is an Organization? - the Nature of Organizations

What Software Architecture Should Look Like • Dave Farley • GOTO 2022

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

Cloud Models - CompTIA Network+ N10-009 - 1.3

Everything Valuable from an MBA in 25 minutes

Microservices with Databases can be challenging...

Why 95% of Android Developers Get Use Cases Wrong

JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue

마이크로서비스란? 비디오를 통한 실용적인 영어 학습 배경

일상 커뮤니케이션에 유용한 상위 5개 표현

비디오를 활용한 쉐도잉 가이드: 단계별 방법

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법