search

dotnetcore / CAP

Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
http://cap.dotnetcore.xyz
MIT License
6.61k stars 1.28k forks source link

support CDC #1574

Closed ductai202 closed 1 month ago

ductai202 commented 1 month ago

Hi, I just ask do we will support CDC (change data capture) with tools like Debezium in the future, and when working with RabbitMQ, can we more flexible config exchange type like Direct, Fanout or Header, now I see we currently only use Topic Exchange. Thanks.

yang-xiaodong commented 1 month ago

Hi,

I just ask do we will support CDC (change data capture) with tools like Debezium in the future.

No plan and no support in the future, that doesn't fit our design.

when working with RabbitMQ, can we more flexible config exchange type like Direct, Fanout or Header, now I see we currently only use Topic Exchange.

We provide an upper level abstraction for the Broker, if you want to be flexible you should use other libraries specialized for RabbitMQ such as EasyNetQ

ductai202 commented 1 month ago

We provide an upper level abstraction for the Broker

what does it really means, can you explain more information

yang-xiaodong commented 1 month ago

The feature we provide requires ensuring that all brokers are available, which may involve utilizing specific functions of a particular broker. This means that when you switch between any supported brokers, the code does not need to be changed, similar to how EF database providers work.

ductai202 commented 1 month ago

I see, thanks for your answer !