|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/transactional-outbox-pattern-with-debezium/
课程评论：没有评论
**课程标题：** 事务性发件箱模式与Debezium **课程概述：** 本课程将深入介绍Debezium，一个用于捕获数据库变更并将其转换为事件流的分布式服务。Debezium能够记录数据库表中每一个行级变更，应用程序只需读取这些事件流，即可按发生顺序响应这些变更。这对于松耦合和可扩展微服务架构至关重要。Debezium支持MongoDB、MySQL、PostgreSQL、Oracle等多种数据库。 **Debezium的优势：** 1. **保证捕获全部数据变更。** 2. **支持广泛的数据库类型。** 3. **低延迟生成变更事件，避免高CPU使用率。** 4. **能够捕获删除操作。** 5. **能够捕获旧记录状态及附加元数据。** **课程内容亮点：** 1. **微服务间数据交换模式：** 学习各种数据交换模式，了解其优缺点。 2. **事务性发件箱模式：** 理解该模式的含义、必要性及多种实现方式。 3. **Debezium详解：** 学习Debezium的架构、MongoDB连接器及其内部工作原理。 4. **实战演示：** 通过开发一个订单服务（接收并存储订单详情）、使用Debezium将详情作为事件流式传输到Kafka，并由忠诚度服务消费这些事件（为客户分配忠诚度积分），从而实现订单服务与忠诚度服务之间的松耦合，并解决双重写入问题。
Debezium is a set of distributed services to capture changes in your databases so that your applications can see those changes and respond to them. Debezium records all row-level changes within each database table in a change event stream, and applications simply read these streams to see the change events in the same order in which they occurred.This is widely used to loosely couple and scale the micro-service architecture. It supports wide range of databases like Mongodb, MySQL, Postgres, Oracle etc.Advantages of Debezium:1. Ensures all data changes are captured.2. Supports wide range of Databases.3. Produces change events with very low delay. Also avoids high CPU usage.4. Can capture deletes.5. Can capture old record state and additional metadata.What to expect from this course:1. Learn about what are different Data Exchange patterns between Microservices, their advantages and disadvantages.2. What is Transactional Outbox Pattern, why is it needed, and what are various ways to implement it?3. What is Debezium, it's architecture, connector for Mongodb and it's internal working.4. Full Hands-on demo, where we will develop order service that accepts and stores order details, stream these details using Debezium as events on Kafka, and then consume these events using loyalty service, that allocates loyalty points to the customer, thus loose coupling dependency between our order service and loyalty service and also avoiding Dual Writes problem!
