我覺得這裏最好的辦法是用卡夫卡連接:link 但它是一個拉的方法: Kafka Connect sources are pull-based for a few reasons. First, although connectors should generally run continuously, making them pull-based means that the connector/Kafka Connect decides when data is actually pulled, which allows for things like pausing connectors without losing data, brief periods of unavailability as connectors are moved, etc. Second, in distributed mode the tasks that pull data may need to be rebalanced across workers, which means they won't have a consistent location or address. While in standalone mode you could guarantee a fixed network endpoint to work with (and point other services at), this doesn't work in distributed mode where tasks can be moving around between workers.
阿雯
我拉的基礎卡夫卡連接方法的優點同意,但考慮到連接器會需要從依賴於客戶端的數量多源拉。我們如何處理這樣配置在連接器源憑據,頻繁增加和客戶的缺失等事物的來源平臺的管理似乎是一個挑戰。我們如何有效地處理這個問題? –