Skip to content

The hardest part of microservices is your data

2017 46 min Red Hat Summit en YouTube

Hear from Christian Posta, Principal Architect, Red Hat in this breakout session at Red Hat Summit 2017. One of the tenants of microservices, and a way to minimize dependencies, is that “a service should own its own database.” This is easier said than done. Why? Because: your data. In working with data in information systems for 5 decades, application developers have accepted the practice of using relational databases and relying on all of their safety guarantees. But, as we build services architectures that span more than one database by design (as with microservices), things get harder. How do we synchronize data across databases, especially heterogeneous data? Developing for the traditional enterprise, we have to build fast-changing systems that are surrounded by legacy systems with complicated domains like finance, insurance, and retail. So, how do we develop and reason about the boundaries in our system to reduce complexity in the domain? In this session, we’ll explore these problems and see how domain driven design (DDD) helps grapple with the domain complexity. We’ll see how DDD concepts like entities and aggregates help us understand boundaries—based on use cases and how transactions are affected. With transactional boundaries, we can more carefully adjust our needs from the CAP theorem to scale out and achieve autonomous systems with eventual strictly ordered consistency. We’ll see how technologies like Apache Kafka, Apache Camel, and Debezium.io can help build the backbone for these types of systems. And finally, we’ll look at a working example that brings all of this together. https://www.redhat.com/en/summit/2017/agenda/session

Chapters

  1. 0:00 Intro
  2. 1:25 Meet Cristian
  3. 2:35 Microservices
  4. 3:51 Optimizing for speed
  5. 4:22 Managing dependencies
  6. 4:53 Implicit dependencies
  7. 5:20 What is data
  8. 6:20 What is a book
  9. 7:35 How to describe a book
  10. 8:30 Domaindriven design
  11. 11:08 No sequel normalization
  12. 13:25 Comfortability
  13. 14:19 Isolation and Autonomy
  14. 14:33 The Path of Problems
  15. 15:29 Asynchronous Networks
  16. 16:48 DataDriven Systems
  17. 24:40 Cap Theorem
  18. 26:20 Consistency Models
  19. 27:38 Baseball
  20. 28:51 Sequential Consistency
  21. 29:51 Relational Database
  22. 29:57 Regular Database
  23. 30:25 Interim Steps
  24. 30:51 The Internet Companies
  25. 32:07 DBZM
  26. 34:36 Kafka Connect
  27. 36:07 Data Federation
  28. 37:10 Domain Driven Design
  29. 37:38 Netflix API Gateway
  30. 39:23 Lets do a demo
Channel
Red Hat Summit
Views
217

More like this