Branch by Abstraction | Designing Event-Driven Microservices

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

The Branch by Abstraction Pattern is a method of trunk-based development. Rather than modifying the code in a separate branch, and merging the results when finished, the idea is to make modifications in the main branch. An abstraction layer is used to ""branch"" the code along an old and new path. This approach has some key advantages, especially when decomposing a monolith.

Check out the Designing Event-Driven Microservices course on Confluent Developer for more details: https://cnfl.io/microservices-101-mod...

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
► Microservices course playlist: https://bit.ly/designing-event-driven...
► Get Started on Confluent Developer: https://cnfl.io/48FnKRB

CHAPTERS
00:00 - Intro
00:18 - Source Control Branching
00:43 - Code Drift
00:58 - Production Issues
01:48 - ECommerce Example
02:05 - Branch by Abstraction
02:46 - Minimizing Drift
03:04 - A/B Testing
04:08 - Vs. The Strangler Fig Pattern
04:55 - 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