Webhooks support to persist data to third party end-points about readyset HOT 3 CLOSED

Thanks @pythonpen ! Have you looked for a solution like this today? Are there any integrations you'd like to use today but can't?

I'll sync with the team and put this on our roadmap, but we're realistically not going to be able to tackle this for a while. Thanks for starting the discussion!

from readyset.

Thanks @jbensal for consideration in the roadmap - Sure, it can be long short. Just made a suggestion only - for having this as an add-on capability in ReadySet.

Today this type of realtime ETL requirements are coded at the application level via webhooks (which works pretty good - but not very reliable sometimes due to bugs in the code or application failures), however if such integrations are moved closer to the DB and can call webhook functions when a db change happens can be more reliable and can ascertain the ACID properties for the DB as well.

For high fidelity data inter-operability applications in the domain of Healthcare (Patient Health Record - inter-ops etc), having such reliable db change based webhook triggers are good.

I don't know yet if such realtime ETL capabilities exists native to the DB - maybe PostREST can do it or Store Procedures can do it, also I know that Supabase and Firebase has these type of function hooks based on db changes.

But having it outside like in a Readyset - can have the potential to proxy these webhook trigger services in DB neutral way. (irrespective of what you use as the DB - like MySQL / Postgres / Supabase etc )

from readyset.

This is a nice problem to solve for - even as a separate product I guess

from readyset.