pgdeltastream

Yep. We experimented around a lot with pub/sub (listen/notify, wal-lr). But it was getting hard to scale and heavy/spiky write loads needed careful thought. This seemed like the right way to get started esp. given that Hasura can get the entire sql query including authz, before moving to tackling that problem more effectively[1]. For folks that want to play around with wal and listen/notify: https://github.com/hasura/pgdeltastream https://github.com/hasura/skor [1] https://github.com/hasura/graphql-engine/blob/master/archite...

> What I'm not seeing is how do you .. You can write fairly complex rules with the access control layer ! The first two conditions are possible (except for the project is only visible on Mondays). allow select on rows which satisfy this property: { "project_type" : { "_eq" : "whatever" } } allow update on rows which satisfy this property: { "closed_data" : { "_is_null" : true } } The idea is simple, we provide a boolean expression based access control layer which can use variables from headers. When you can't specify it using the access control layer, you can write this in your own graphql layer and schema stitch with hasura. So you only have to write what is not possible with the access control layer. > The other point I don't see is how do you ... You can use the tooling around Postgres ! You can create an `ON INSERT` trigg