ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #postgresql
Decide which Jaeger backend—Cassandra, Elasticsearch, or PostgreSQL—fits your scale and operational needs. This guide compares write/read paths, scalability, and pagination, then walks through a concrete Cassandra deployment and validation steps.
Learn when a jsonb_path_ops GIN index gives faster containment queries with less write‑induced bloat, and how to tune pending‑list limits and autovacuum for write‑heavy PostgreSQL workloads.
YugabyteDB’s UPSERT works like PostgreSQL’s INSERT … ON CONFLICT, but it’s implemented as a single Paxos proposal per key. This gives ACID guarantees across shards, yet high contention can spike latency. Learn how to use it safely, verify it, and know the trade‑offs.
Decide whether to expose a database port with SSL/TLS, tunnel through a bastion host, or combine both in DataGrip.
Use Knex transactions to keep related writes atomic, pass the transaction object to every query, and watch your connection pool.
Implement database-level multi-tenancy using PostgreSQL Row Level Security (RLS) to enforce data isolation without relying on application-tier middleware.
Learn how PostgreSQL’s JSONB expression indexes can cut nested JSON query times from seconds to milliseconds. A practical guide with examples, trade‑offs, and next‑step actions.
Large write‑heavy tables cause slow inserts, full scans, and long vacuums. PostgreSQL’s declarative partitioning splits a table into smaller pieces, enabling partition pruning, targeted maintenance, and faster queries. This post walks through a concrete example and highlights trade‑offs.
Minimal single-region architecture for a Scalingo web app using a managed PostgreSQL add-on over private networking, with requirements, trust boundaries, ops checks and failure modes.
cassandra
elasticsearch
yugabytedb
datagrip
nodejs
knexjs
supabase
scalingo