Rudderstack VS debezium

If CDP(such as RudderStack) were a restaurant, then Data Integration is the guy that gets all raw ingrediants from different shops and makes it available to Chef that sorts and combines raw ingrediants to make a dish. The chef can't cook anything without raw ingrediamt. Similarly Data Integration is also an important component in CDP that collects customer data from various sources and them other components unify it and activate it.

More details on GitHub repository - https://github.com/rudderlabs/rudder-server

Are you RudderStack?

In bigger setups, all you want is a data collector and router so that you can feed the data into multiple destinations, depending on the use case. Analytics is just one. Example: https://www.rudderstack.com/ & https://www.rudderstack.com/replace-google-analytics-4-guide...

Check out RudderStack, a Go project to build data pipeline. Our slack is quite active. The best way to contribute is by creating a new integration with your favorite tool. You do not need to rely to too much on existing knowledge about inner workings of the project to do so, so it is beginner friendly.

Interesting. About "Redshift need google sheet sync to table", wouldn't this be more aligned with the responsibility of a CDP(such as RudderStack) as opposed to something we expext a warehouse to do?

The challenge is over. Winners have been announced. When we are ready for the next one, will announce on RudderStack GitHub repo

Super. This is amazing. Sharing your project with the community. If you get a chance, try out RudderStack to build your pipeline.

They manage data in the application layer and your original data stays where it is. This way data consistency is no longer an issue as it was with streaming databases. You can use Change Data Capture (CDC) services like Debezium by directly connecting to your primary database, doing computational work, and saving the result back or sending real-time data to output streams.

Both of these articles mention a key player, Debezium. In fact, Debezium has had a place in the modern infrastructure. Let's use a diagram to understand why.

This might be overkill, but you could use an extra tool like https://debezium.io to capture logs about all creates, updates, and deletes in your table

If you're considering a relational database for an event-driven architecture, check out Debezium. It lets you stream changes to relational databases, and subscribe to change events.

Debezium

https://debezium.io/ comes to mind as an open source product, but there are a gazillion of these tools out there.

Contrary to what it sounds, it’s quite straightforward. The database changes are captured via Debezium and published as events on Apache Kafka. ClickHouse consumes those changes in partial order by Kafka Engine. Real-time and eventually consistent.