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

How do we know whether Event-Driven Microservices are the right solution? This is the question that Tributary Bank faced when they looked at modernizing their old fraud-detection system. They were faced with many challenges, including scalability, reliability, and security. Some members of their team felt that switching to an event-driven microservice architecture would be the magic bullet that would solve all of their problems. But is there any such thing as a magic bullet? Let's take a look at the types of decisions Tributary Bank had to make as they started down this path.

To learn more about Microservices, check out my Designing Event-Driven Microservices course on Confluent Developer: https://cnfl.io/microservices-101-module-1

RELATED RESOURCES
► 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

00:45 - Common problems in a monolithic application

01:59 - Creating isolation in microservices

03:36 - Building resilient microservices

05:49 - Improving the performance of your system

07:39 - Reducing the impact of security breaches

08:59 - Polyglot Architecture

09:56 - Conclusion

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 #eventdrivenarchitecture #apachekafka #kafka #confluent