ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: 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

วิดีโอแนะนำ

184 ประโยค

Microservices explained - the What, Why and How?

Business EnglishUniversity StudentsWorking Adults

120 ประโยค

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

Business EnglishUniversity StudentsWorking Adults

43 ประโยค

What is an Organization? - the Nature of Organizations

Business EnglishUniversity StudentsWorking Adults

18 ประโยค

SD91: Reliability vs Scalability

Business EnglishUniversity StudentsWorking Adults

210 ประโยค

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

Business EnglishUniversity StudentsWorking Adults

309 ประโยค

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

Business EnglishUniversity StudentsWorking Adults

315 ประโยค

how AI broke the SWE Career Ladder

Business EnglishInterview EnglishUniversity Students

51 ประโยค

Cloud Models - CompTIA Network+ N10-009 - 1.3

Business EnglishUniversity StudentsWorking Adults

480 ประโยค

Everything Valuable from an MBA in 25 minutes

Business EnglishUniversity StudentsWorking Adults

42 ประโยค

System Design: How to Build an API Rate Limiter

Business EnglishUniversity StudentsWorking Adults

279 ประโยค

Microservices with Databases can be challenging...

Daily ConversationUniversity StudentsWorking Adults

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

เทคนิค shadowing: อ่านคู่มือฉบับเต็มทีละขั้นตอน →

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: What Are Microservices Really All About? (And When Not To Use It)

เลือกโหมดฝึก

ดาวน์โหลดแอป

ช่องเดียวกัน

The Secret Sauce Behind NoSQL: LSM Tree

Proxy vs Reverse Proxy (Real-world Examples)

Cache Systems Every Developer Should Know

Top 5 Redis Use Cases

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 fast?

Kubernetes Explained in 6 Minutes | k8s Architecture

System Design: Why is Kafka Popular?

What is API Gateway?

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

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

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

SD91: Reliability vs Scalability

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

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

how AI broke the SWE Career Ladder

Cloud Models - CompTIA Network+ N10-009 - 1.3

Everything Valuable from an MBA in 25 minutes

System Design: How to Build an API Rate Limiter

Microservices with Databases can be challenging...

เป้าหมายการพูดสำหรับคลิปนี้

คลังวลี

ปรับปรุงจุดอ่อนของคุณ

เทคนิค Shadowing คืออะไร?