/ THE FEED /
Deep, recent reads ranked by depth and freshness.
01PlanetScale · architecture
Designing a sharded Postgres architecture requires grouping tables around shared query keys rather than starting from table structures alone. The post details how to configure shard groups, reference tables, SQL expressions in shard indexes, and global secondary indexes using Neki. This setup enables efficient single-shard queries and transactions while maintaining full Postgres semantics.
DEPTH ■■■■■8 min read2 days ago
02Grab · architecture
To maintain app stability amidst rapid weekly releases and AI-generated code, Grab uses a layered defense strategy covering prevention, release gates, and incident response. This pipeline includes static analysis via custom lint rules, multiple tiers of automated and manual testing, a pre-production early access build, staged rollouts, and feature flags with instant kill switches. As a result, critical defects are caught early in the development lifecycle before reaching the wider production user base.
DEPTH ■■■■■16 min read4 days ago
03PlanetScale · practice
Postgres ON DELETE CASCADE can cause production outages, replication failures, and performance degradation during large deletions or schema migrations due to long-running transactions holding locks and generating massive WAL. The author recommends using soft deletes with batched background cleanup instead to keep transactions short and bounded. This approach avoids table locks and simplifies data recovery.
DEPTH ■■■■■5 min read4 days ago
04PlanetScale · architecture
This post examines how PostgreSQL uses TOAST to manage oversized rows and variable-length columns through compression and off-row storage. It compares the pglz and LZ4 compression algorithms across different workloads, highlighting trade-offs in search windows, file sizes, and CPU overhead. The analysis demonstrates how these mechanisms impact storage efficiency and read performance for large text and JSON data.
DEPTH ■■■■■12 min read13 days ago
05Stack Overflow · practice
Standard regression tests usually only verify developer intent rather than the actual, unwritten behaviors that systems accumulate in production over time. By capturing real production traffic and network-level interactions, teams can build characterization test suites to automatically detect unintended behavioral shifts. This approach prevents accidental regressions during legacy refactoring, rewrites, and major framework upgrades.
DEPTH ■■■■■6 min read3 days ago
06PlanetScale · performance
Following competitive benchmarks that highlighted opportunities for optimization, the developers of the TIN full-text search index for Postgres released versions 1.0.4 and 1.0.6. These updates added Snowball stemming for 18 languages, optimized top-k sorting queries with deterministic tiebreakers, and improved overall query performance. As a result, benchmark tests show that TIN outperforms competing extensions across conjunction, disjunction, and phrase query workloads.
DEPTH ■■■■■8 min read2 weeks ago
07Stack Overflow · practice
Researchers analyzed thousands of job postings to understand how artificial intelligence is changing technical skill requirements. The findings indicate that instead of creating a workforce of pure generalists, the market is developing distinct new specialized skill bundles and hybrid roles. Consequently, organizations are facing talent debt as the half-life of technical skills rapidly shrinks.
DEPTH ■■■■■15 min read11 days ago
08Grab · architecture
Grab addressed runtime data reliability issues in its data mesh by implementing automated Data Production Issues (DPIs). The system uses an incident orchestrator to detect contract breaches, a Data Health API for cross-platform root cause analysis, and Hugo for automated remediation. This approach resolved 86.9 percent of incidents automatically and made mean time to resolve six times faster.
DEPTH ■■■■■12 min read8 weeks ago
09Stack Overflow · practice
This post discusses the challenges and methods of applying observability to AI agents, which combine traditional distributed systems telemetry with new requirements for monitoring LLMs and multi-step tool calls. The discussion highlights how non-deterministic agent behavior and increased speed of execution make continuous production feedback loops essential for upstream development. Ultimately, integrating observability data into automated testing and development loops helps teams iterate on agent performance.
DEPTH ■■■■■25 min read2 weeks ago
10PlanetScale · scaling
Growing applications often encounter hot shards when certain tenants or data subsets outgrow initial sharding strategies based on workspace IDs. To mitigate this, teams can scale up resources, isolate large tenants into specific key ranges, or fundamentally change the shard key for problematic tables based on access patterns. Neki facilitates these adjustments by allowing declarative data topologies and online resharding without downtime.
DEPTH ■■■■■7 min read3 weeks ago
