► LEARN MORE: https://cnfl.io/microservices-101-module-1

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.

Check out the Microservices 101 course on Confluent Developer for more details: https://cnfl.io/microservices-101-module-1

RELATED RESOURCES
► Topics | Apache Kafka® 101: https://youtu.be/kj9JH3ZdsBQ
► Introduction to Apache Kafka Partitions | Apache Kafka® 101: https://youtu.be/y9BStKvVzSs
► Consumers | Apache Kafka® 101: https://youtu.be/Z9g4jMQwog0
► Microservices: An Introduction https://cnfl.io/3ZMt3up
► Event-Driven Microservices Architecture: https://cnfl.io/48FSYbj
► Migrate from Monoliths to Event-Driven Microservices: https://cnfl.io/3tsqlhu

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
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.

#microservices #apachekafka #kafka #confluent