Upcoming Online Meetup: A Change-Data-Capture use-case: Designing an Evergreen Cache

Your app is slow? Just cache your SQL database queries, right? Even if you have inherent database design flaws or query structure issues, caching will most likely solve your problem. Pat yourself on the shoulder and go grab a cookie.

But wait, what if your app is not the only thing that writes to the DB? Okay, well, we can always do polling, execute DB triggers, etc… Let’s face it though — it all works until it doesn’t.

Enter Change-Data-Capture. With it, a DB can send change events (SELECT, DELETE and UPDATE) which you can then register to. Think of it as an opposite to Event Sourcing that aggregates events to produce state — CDC is about getting events out of states. Once CDC is implemented, you can subscribe to events and update cache accordingly!

Intrigued? Join us for a meetup with Nicolas Fränkel. Nicolas will describe an easy-to-setup architecture that leverages CDC to create an evergreen cache:

https://www.meetup.com/at-wix/events/271641848/