by flippy_flops on 11/26/23, 6:14 PM with 3 comments
1. Our clients struggle to access "live" data as we don't offer web-hooks. 2. We don't provide data with applied business logic, such as status reports.
Of course we could (should?) build those things but (A) building/maintaining a web-hook service seems daunting and (B) it feels suboptimal.
The goal is to provide real-time read-only data where my clients don't each have to implement data-sync.
In my head, it feels like we should give each client a small, read-only Postgres instance where we keep updated reports and fairly denormalized data. Then they can just hook into it and setup their own watchers, etc. If they need more muscle, then they replicate it to their own instance. But is there something "better" I could provide?
SupaBase seems close, but again - that's both us and our clients having intimate knowledge of propriatary tooling - whereas SQL (Postgres) is nearly universally known.
So if you were trying to provide realtime data and reports to a bunch of SAAS client IT groups, how would you provide it?
by bluepuma77 on 11/29/23, 9:08 PM
by throwaway_1987 on 11/27/23, 9:52 AM
Your customers would populate the older data using your existing API, but then switch to the queue for new updates.
by rattray on 11/26/23, 11:39 PM
Have you looked at svix.com ? (I have no affiliation)