- Throughput/latency: pg_stat_statements [1] or Prometheus' exporter [2]
- A/B tests: aren't these frontend things? recording which version a user got is an INSERT
- Auth: row-level security [3] and session variables
- Tracing, shadow traffic: I don't think these are relevant in a "ship your database" setup.
- Valdation: check constraints [4] and triggers [5]
Maybe by some measures they're "not quite as good", but on the other hand you get them for free with PostgreSQL. I've lost count of how many bad internal versions of this stuff I've built.
- Throughput/latency: pg_stat_statements [1] or Prometheus' exporter [2]
- A/B tests: aren't these frontend things? recording which version a user got is an INSERT
- Auth: row-level security [3] and session variables
- Tracing, shadow traffic: I don't think these are relevant in a "ship your database" setup.
- Valdation: check constraints [4] and triggers [5]
Maybe by some measures they're "not quite as good", but on the other hand you get them for free with PostgreSQL. I've lost count of how many bad internal versions of this stuff I've built.
[0]: https://severalnines.com/blog/postgresql-audit-logging-best-...
[1]: https://www.postgresql.org/docs/current/pgstatstatements.htm...
[2]: https://grafana.com/oss/prometheus/exporters/postgres-export...
[3]: https://www.postgresql.org/docs/15/ddl-rowsecurity.html
[4]: https://www.postgresql.org/docs/15/ddl-constraints.html
[5]: https://www.postgresql.org/docs/15/plpgsql-trigger.html