thin-backend-todo-app VS metagration

In the early development phase we actually added GraphQL support to Thin. It was removed as we figured out that a lot of the common CRUD operations would take a lot more boilerplate code when doing it with GraphQL. Now our API consists of high level functions like `createRecord(tableName, object)` and `useQuery(query(tableName))`. You can find some example code here: https://github.com/digitallyinduced/thin-backend-todo-app/blob/main/app.tsx

If you want to play around with Thin, you can find a small example app here. It's running on Vercel here.

If you're looking for something like GraphJin, PostGraphile or Hasura but with less boilerplate and complexity, more end-to-end typesafe approach and optimistic updates, check out Thin Backend https://thin.dev/ (https://github.com/digitallyinduced/thin-backend)

Thin Backend takes a bit more of a higher level approach to database operations than services like GraphJin, but solves fundamentally the same problem. Doing things in a more structured way also allows us to do things like optimistic updates by default that require manual work with GraphQL tools.

To see some code examples, here's a small example project done with thin-backend: https://github.com/digitallyinduced/thin-backend-todo-app It's running on Vercel here: https://thin-backend-todo-app.vercel.app/

} ``` Live example here: https://thin-backend-todo-app.vercel.app/ Full Code: https://github.com/digitallyinduced/thin-backend-todo-app

Realtime uses logical replication, and from your link it looks like it should work with Timescale (although not recommended):

> Using logical replication with TimescaleDB is not recommended, as it requires schema synchronization between the primary and replica nodes and replicating partition root tables, which are not currently supported.

As long as logical replication is supported, this won't be an issue for Realtime because the purpose is to receive data changes (which come in a JSON format) and the end-user doesn't need to persist schema modifications.

> but couldn't get it working

If you send me some error logs, I can take a look or forward to one of the team.

> support Postgres streaming replication

This is the first time I've heard it requested - I don't think it's something we'd do unless there was a good reason and strong demand. If we were to do any work in this direction we'd prefer to try contribute DDL streaming to PostgreSQL's logical streaming. We've been thinking about this for a while (Michel has built metagration - https://github.com/michelp/metagration which has prompted a few ideas for core patches)