How To Build Scalable and Resilient Microservices | Designing Event-Driven Microservices

preview_player
Показать описание

Building scalable and resilient microservices requires an approach that eliminates the need to treat them as special. They should be treated as easily replaceable building blocks. This means eliminating bottlenecks and single points of failure but it can also mean changing from a pull-based approach to a push-based approach.

RELATED RESOURCES

CHAPTERS
00:00 - Intro
01:29 - Why Allow for Failure?
01:48 - What are Persistent Topics?
02:31 - What is a Scale to Zero Approach?
02:54 - How to Avoid Bottlenecks?
03:21 - What are the Benefits of Kafka Partitions?
03:52 - Why Avoid Single Points of Contention?
04:19 - How to Set Up Multiple Consumers?
04:54 - Closing
--
ABOUT CONFLUENT

#microservices #apachekafka #kafka #confluent
Рекомендации по теме
Комментарии
Автор

Wade here: This was a fun video. You can see my face light up when I bring in my special guest. I brought him on because I wanted to come up with an alternative metaphor for the "pets" vs "cattle" that you often hear in the industry. What do you think? Does this metaphor work? Do you like it more than pets vs cattle?

ConfluentDevXTeam