Disclaimer: I am cofounder of Bruin (<a href="https://github.com/bruin-data/bruin" rel="nofollow">https://github.com/bruin-data/bruin</a>), we are a competitor to Erathos.<p>It seems like a relatively straightforward marketing article. I was pleasantly surprised to learn about Erathos though, nice product!<p>I am personally not a big fan of CDC in prod. Streaming data movement is generally prone to confusion, and it feeds into bad data patterns like hard deletes without any audit logs, no timestamps on updates or deletes, etc. which are usually the reason why batch loads cannot be utilized. They require a decent operational understanding of the underlying database, and have some gotchas like the Erathos folks mentioned in the article. We offer CDC both in our cloud platform, as well our open-source tools, but if I could, I would always pick an incremental batch load with a cursor value over a CDC connection.<p>I understand it is sometimes required due to organizational complexity or legacy database reasons, mine is just a personal preference.<p>If anyone is looking for an open-source CDC tool that runs as a standalone Go CLI, check out ingestr: <a href="https://github.com/bruin-data/ingestr" rel="nofollow">https://github.com/bruin-data/ingestr</a>