Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Supabase Pipelines. Your app runs on Postgres, but your analytics usually live somewhere else, like BigQuery. Pipelines keeps that data in sync for you in near real time, with no pipeline to build or maintain.

63,426 просмотров • 3 месяцев назад •via X (Twitter)

Комментарии: 21

Фото профиля Supabase
Supabase3 месяцев назад

It's built on Postgres logical replication, powered by our open-source engine, Supabase ETL. It runs the initial sync, replicates every insert, update, delete, and truncate, and keeps your destination schema in sync as your Postgres schema changes. BigQuery is live now. ClickHouse, Snowflake, and DuckLake are available on request. Read more:

Фото профиля Supabase
Supabase3 месяцев назад

Tune into our weekly livestream on Mondays at 23:00 UTC to ask questions and talk about Supabase Pipelines.

Фото профиля Mojeeb | Arcapush.com
Mojeeb | Arcapush.com3 месяцев назад

amazing! i’ll set this up, right away.

Фото профиля Tech PlusX
Tech PlusX3 месяцев назад

👀👀

Фото профиля Hixon
Hixon3 месяцев назад

Love anything Supabase does

Фото профиля Jaya Nayak
Jaya Nayak3 месяцев назад

No more wasting engineering hours building custom data pipelines.

Фото профиля Layerbase
Layerbase3 месяцев назад

Clickhouse on Layerbase has been a hit. Surprised it took this long

Фото профиля Samian
Samian3 месяцев назад

so you're telling me my bigquery pipeline built on a cron job and a prayer was unnecessary this whole time

Фото профиля AI Mastery Guide
AI Mastery Guide3 месяцев назад

Keeping Postgres and BigQuery in sync automatically saves so much hassle

Фото профиля Sebastian Buzdugan
Sebastian Buzdugan3 месяцев назад

near real time breaks first on schema drift not raw replication speed

Фото профиля skellertor
skellertor3 месяцев назад

Glad I was forced to use you for a project. Never looking back now

Фото профиля Marco
Marco3 месяцев назад

Right now im using GCP DataStream for this. Is this in any way better, faster or cheaper?

Фото профиля Hussain Fakhruddin
Hussain Fakhruddin3 месяцев назад

No pipeline to build or maintain is the real win.

Фото профиля Carmelo schepis
Carmelo schepis3 месяцев назад

why sync when you could just not

Фото профиля Mathieu Kessler
Mathieu Kessler3 месяцев назад

No pipeline to build or maintain is the real win.

Фото профиля Fabio Lauria
Fabio Lauria3 месяцев назад

Most teams waste weeks shuffling data between systems instead of analyzing it. The real bottleneck isn't the pipeline—it's converting synced data into actionable decisions quickly enough to drive impact. I focus on delivering insights in minutes, not days waiting for analytics teams to surface them 📊

Фото профиля Guru Meditation
Guru Meditation3 месяцев назад

Is that similar to ClickPipes?

Фото профиля Camaleón Raro
Camaleón Raro3 месяцев назад

real-time pipelines without building one is the actual unlock. most teams i know spend 60% of analytics eng time on the sync layer the failure mode nobody talks about: schema drift between postgres and bigquery. thats where every pipeline I've seen buckle after 3-4 months

Фото профиля MixRoute AI
MixRoute AI3 месяцев назад

Love to see any new features Supabase adds.

Фото профиля Emile Kratiroff
Emile Kratiroff3 месяцев назад

No app big enough to have analytics on big query runs on supabase

Фото профиля Valenciana
Valenciana3 месяцев назад

@grok what does this mean for my backend in simple terms

Похожие видео

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!

Akshay 🚀

65,672 просмотров • 11 месяцев назад