3 ms·

I’d love to see some overlap/collab with Supabase here. If Timescale is providing databases I don’t have to monkey with that scales to my workload, and Supabase

I’d love to see some overlap/collab with Supabase here. If Timescale is providing databases I don’t have to monkey with that scales to my workload, and Supabase is proving Firebase-like ergonomics and DX, there’s some strong synergy here. Supabase as an add on to Timescale Cloud or Timescale as a supported alternate provider for Supabase would be compelling for get-it-done devs and teams out there

CameronNemo 5y ago
There are a lot of interesting postgres front ends that could be useful. Supabase, metabase, postgrest, hasura. https://supabase.io/ https://supabase.io/ https://www.metabase.com/ https://www.metabase.com/ https://postgrest.org/ https://postgrest.org/ https://hasura.io/ https://hasura.io/ Of course grafana too, but that goes beyond just PostgreSQL.
Aarvay 5y ago
Unfortunately Timescale's license is the blocker - https://news.ycombinator.com/item?id=25299128 https://news.ycombinator.com/item?id=25299128
- kiwicopple 5y ago
  yes, we'd love to offer Timescale as an extension, but still waiting for buy-in from the Timescale team on this. If we can't manage we'll eventually do something else for timeseries data - eg, we could do a Foreign Data Wrapper to Clickhouse tables
  - qoega 5y ago
    Why use FDW if you can work with ClickHouse directly? What is the use case? By the way I can see there are some already but I do not use them https://github.com/Infinidat/infi.clickhouse_fdw/ https://github.com/Infinidat/infi.clickhouse_fdw/ https://github.com/adjust/clickhouse_fdw https://github.com/adjust/clickhouse_fdw
    - kiwicopple 5y ago
      > Why use FDW It would be beneficial to couple transactional data (Postgres) with OLAP data (CH). There are a few other things coming in PG which might mitigate the need for CH too (pluggable storage, zheap), so we're not going to rush this part.

3 ms·

I’d love to see some overlap/collab with Supabase here. If Timescale is providing databases I don’t have to monkey with that scales to my workload, and Supabase

by hardwaresofton 5y ago

CameronNemo 5y ago
There are a lot of interesting postgres front ends that could be useful. Supabase, metabase, postgrest, hasura. https://supabase.io/ https://supabase.io/ https://www.metabase.com/ https://www.metabase.com/ https://postgrest.org/ https://postgrest.org/ https://hasura.io/ https://hasura.io/ Of course grafana too, but that goes beyond just PostgreSQL.
Aarvay 5y ago
Unfortunately Timescale's license is the blocker - https://news.ycombinator.com/item?id=25299128 https://news.ycombinator.com/item?id=25299128
- kiwicopple 5y ago
  yes, we'd love to offer Timescale as an extension, but still waiting for buy-in from the Timescale team on this. If we can't manage we'll eventually do something else for timeseries data - eg, we could do a Foreign Data Wrapper to Clickhouse tables
  - qoega 5y ago
    Why use FDW if you can work with ClickHouse directly? What is the use case? By the way I can see there are some already but I do not use them https://github.com/Infinidat/infi.clickhouse_fdw/ https://github.com/Infinidat/infi.clickhouse_fdw/ https://github.com/adjust/clickhouse_fdw https://github.com/adjust/clickhouse_fdw
    - kiwicopple 5y ago
      > Why use FDW It would be beneficial to couple transactional data (Postgres) with OLAP data (CH). There are a few other things coming in PG which might mitigate the need for CH too (pluggable storage, zheap), so we're not going to rush this part.