Introduction

In simple words: Each time a new event occurs on a specific table, such as INSERT / UPDATE / DELETE, an event will be created and, if configured – published to a destination so some service will be notified for it.

The master guide for
Change-data-capture We crafted a 4-part series of tutorials to help you understand, build, and rule production-grade change-data-capture pipelines! Part 1

Flow

1. Sign up to Memphis.dev Cloud or Deploy Memphis OS
2. Create a new Supabase table.
3. Configure a webhook for the newly created table.
4. Check the incoming CDC events in Memphis.

Step 1: Prepare your Memphis.dev Account

In this tutorial, we will focus on using Memphis.dev Cloud, but the following steps should be similar when using Memphis.dev OS as well.

Once an account has been created, please head to the users section and create a new client-type application:

Step 2: Create a new Supabase table

Step 3: Configure a webhook for the newly created table

Head to Database -> Webhooks -> Create a webhook

A change-data-capture event can occur and be sent for every “INSERT”, “UPDATE”, and/or “DELETE” command that takes place in the configured table.

Configure the webhook based on your use case requirements –

• Method: POST
• URL: https://aws-eu-central-1.restgw.cloud.memphis.dev/stations/supabase/produce/single
• Headers:
  • Content-type: application/json
  • Authorization: Bearer <JWT Token>

Step 4: Check for incoming CDC events

Insert a new record into the created Supabase table. Because we selected the INSERT type of events, it should output an event.

Return to the Memphis dashboard and into the “supabase” station and check the center panel –
events can be seen in the center panel, and the parsed payload on the right-bottom.

CDC + Schema enfrocement = Production Schema changes can easily break your pipeline. Watch RJ's Schemaverse walkthrough to learn how to avoid it. Watch