search

questdb / roadmap

QuestDB Public Roadmap
6 stars 0 forks source link

Change Data Capture #28

Open pswu11 opened 1 year ago

pswu11 commented 1 year ago

Summary

For some use cases, it's convenient if there's a way for developers to listen to database changes instead of pulling them proactively. This could be possible if we add support for CDC by integrating with Debezium.

Once we have replication, it might be relatively easier to add this feature (see https://github.com/questdb/questdb/issues/2252). So this feature depends on:

Expected outcome

An optional function for users to subscribe to database changes on the table level.

Do you need this feature?

This feature is currently just an idea that we are considering. If this is interesting/important/critical to your use case, share your feedback with us by commenting below. Thank you!

Luyang2902 commented 1 year ago

This feature is very import to my stocks picking project ! I want to integrate the questdb with Materialize

kfollesdal commented 5 months ago

Questdb together with Materialize will be a very powerful combination 💯 But since Questdb is Postgresql wire protocol compatiblel and Materialize support Postgres via Logical replication. It is more effective for Materialize to use logical replication then Debezium for postgres connection.

kzk2000 commented 1 month ago

This feature would make QuestDB the perfect persistence layer for https://deephaven.io/ to avoid continuous polling from QuestDb - very much looking forward to this!