freeCodeCamp·5wLearn Software System Design
A free 2-hour freeCodeCamp course on software system design covering foundational to production-ready concepts. Topics include database types (SQL, NoSQL, Graph), vertical vs horizontal scaling, load balancing, health checks, single points of failure, API design and protocols (REST, GraphQL), TCP/UDP transport layer, authentication, authorization, and security.
The Coding Gopher·6wI replaced my entire stack with Postgres...
PostgreSQL can replace a surprising number of specialized services in a typical tech stack. JSONB with GIN indexes handles NoSQL-style document storage, SELECT FOR UPDATE SKIP LOCKED turns a table into a concurrent job queue, tsvector/tsquery plus pg_trgm power full-text and fuzzy search, and the pgvector extension with HNSW indexes enables vector similarity search alongside relational data. PostGIS covers geospatial queries, declarative partitioning with BRIN indexes handles time-series workloads, materialized views replace basic data warehouse dashboards, and tools like PostgREST or pg_graphql auto-generate APIs directly from the schema. The post acknowledges limits: horizontal sharding at extreme scale and sub-millisecond in-memory caching still warrant specialized tools, but for most applications PostgreSQL alone is a cost-effective, battle-tested foundation.
databricks·7wHow agentic software development will change databases
Agentic software development is reshaping database requirements in three key ways: evolutionary branching (agents create and discard database branches rapidly, with some projects reaching 500+ iterations), scale-to-zero economics (half of agentic app databases have compute lifetimes under 10 seconds, making fixed-cost databases unviable), and openness (agents trained on open-source ecosystems like Postgres operate more reliably with open interfaces and storage formats). Databricks's Lakebase addresses these needs with O(1) copy-on-write branching, sub-second scale-to-zero elasticity, and open Postgres page format storage on cloud object storage. A telling data point: AI agents in Lakebase now create roughly 4x more databases than human users.
System Design Codex·7wWhat is the BFF Pattern?
The Backends-for-Frontends (BFF) pattern involves creating dedicated API gateways for each client type (web, mobile, partner APIs). Each BFF acts as a specialized intermediary that handles client-specific concerns like rate limiting, authentication, caching, and header sanitization. Key advantages include improved resiliency through isolation, client-specific optimization, and faster development velocity. Drawbacks include potential code duplication, growing complexity, and BFF proliferation. Best practices recommend clearly defining client requirements, extracting shared logic into libraries, maintaining clear boundaries, and monitoring performance.
Hacker News·4wFastCGI: 30 Years Old and Still the Better Protocol for Reverse Proxies
FastCGI, the 30-year-old protocol, is argued to be a safer alternative to HTTP for reverse proxy-to-backend communication. HTTP/1.1's ambiguous framing enables desync/request-smuggling attacks, and its lack of structural separation between trusted proxy headers and untrusted client headers creates persistent security vulnerabilities. FastCGI solves both problems: it uses explicit message framing (eliminating desync), and prefixes HTTP headers with 'HTTP_' to structurally separate them from trusted proxy parameters like REMOTE_ADDR. Popular proxies (nginx, Apache, Caddy, HAProxy) support FastCGI backends, and Go's standard library makes switching trivial. Downsides include no WebSocket support, less tooling, and potentially lower throughput due to less optimization.
Vercel·7wQuery and manage Marketplace databases from the dashboard
Vercel now lets developers run SQL queries, view and edit table data, and inspect database schemas directly from the Vercel dashboard. The feature supports marketplace integrations including AWS Aurora Postgres, Neon, Prisma, and Supabase. Three new tabs are added to the integration resource page: Query (run SQL, export as CSV/JSON/Markdown), Data Editor (spreadsheet-like row editing with atomic commits), and Schema (visual graph of tables and relations). Currently available to users with Owner permissions.
Yelp Engineering·6wZero downtime Upgrade: Yelp’s Cassandra 4.x Upgrade Story
Yelp's Database Reliability Engineering team upgraded over a thousand Cassandra nodes from version 3.11 to 4.1 with zero downtime. The post covers their upgrade strategy including benchmarking (4% p99 latency improvement, 11% throughput gain, up to 58% p99 reduction on key clusters), compatibility challenges with Stargate proxy and Cassandra Source Connector, and a three-stage automated upgrade process (pre-flight, flight, post-flight). Key lessons include a Stargate 2.x regression causing slower range queries (resolved by downgrading to 1.x), schema disagreement on CDC-enabled clusters, and the value of running version-specific components in parallel during the transition. The upgrade was performed in-place via rolling restart on Kubernetes, avoiding the cost and complexity of a separate DC approach.
The Developing Dev·6wAWS Distinguished Eng: Learnings From 3000 Incidents And How Engineering Is Changing
Marc Brooker, AWS Distinguished Engineer, shares insights from reading 3,000+ cloud system postmortems, covering what makes great postmortems, why on-call is a powerful learning tool, and how AWS's weekly COE review has been central to its success. He explains why caches can be dangerous in distributed systems due to metastable failures, and how Aurora DSQL was designed to avoid common relational database outage patterns using MVCC and optimistic locking. He also shares his perspective on how AI will reshape software engineering careers, advising junior engineers to focus on understanding customers and problems, and senior engineers to stay hands-on with modern agentic tools. He also advocates for writing as a tool for both scaling expertise and sharpening thinking.
Google Open Source Blog·8wGoogle Cloud: Investing in the future of PostgreSQL
Google Cloud engineers summarize their PostgreSQL upstream contributions from July–December 2025. Key work includes automatic conflict detection for active-active replication, logical replication of sequences, a self-deadlock fix in DROP SUBSCRIPTION, pg_upgrade optimizations for large objects and logical slots, and several bug fixes in pgstattuple, dynamic library loading, and WAL flush functions. The team is also developing a conflict log table, parallel pg_dump for large tables, and pipe-based parallel export. Dilip Kumar was selected for the PGConf.dev 2026 Program Committee.
Neon·4wIntroducing Organization Spending Limits
Neon is introducing spending limits for organizations on paid plans. Users can set a monthly dollar threshold in the Billing console, and Neon will send email alerts at 80% and 100% of the limit. A progress bar tracks current spend, and checks run every 15 minutes. A forthcoming 'Suspend projects' option will automatically pause all project computes when the limit is reached, providing a hard guardrail against runaway costs. The feature requires no external monitoring setup and is managed entirely within the Neon console.
freeCodeCamp·6wSystem Design Course – APIs, Databases, Caching, CDNs, Load Balancing & Production Infra
A comprehensive system design course covering the core concepts needed to transition from mid-level to senior engineer. Topics include single-server to multi-server architecture evolution, SQL vs NoSQL database selection, vertical vs horizontal scaling, load balancing algorithms (round robin, least connections, IP hash, consistent hashing), API styles (REST, GraphQL, gRPC), API protocols (HTTP/HTTPS, WebSockets, AMQP, gRPC), and API design principles. The course emphasizes practical, real-world applicability for both production systems and system design interviews.
Supabase·7w100,000 GitHub stars
Supabase has reached 100,000 GitHub stars and now serves 8 million developers. Founded in 2020 with just two people and a Postgres database, the team reflects on their open-source philosophy of supporting existing tools and communities rather than building everything from scratch. Key open-source projects powering the platform include Postgres, PostgREST, pgvector, Deno, imgproxy, and Elixir Phoenix Framework. The milestone is framed as a community achievement, with future goals centered on making Postgres the default database for every new project on the internet.
InfoWorld·7wBringing databases and Kubernetes together
Running databases on Kubernetes is increasingly common, but Day 2 operational challenges like backup, failover, and resilience remain difficult. Cloud DBaaS solves these problems but creates vendor lock-in. Kubernetes Operators can provide equivalent functionality without lock-in, but doing so consistently across all databases is hard. Percona's Everest project has been donated to the CNCF and rebranded as OpenEverest — a fully open source platform for automating database provisioning and management on any Kubernetes infrastructure, with community-driven support for additional databases over time.
Neon·7wNeon works with Stripe Projects for agentic provisioning
Neon is joining the developer preview of Stripe Projects as a co-design partner, enabling AI coding agents and developers to provision real Postgres databases directly from the terminal via CLI commands. Running `stripe projects add neon` creates a Neon account, provisions a database, and returns connection credentials to the environment automatically. The integration addresses a key gap in agentic workflows: agents could write code but couldn't autonomously set up real infrastructure. Neon is positioned as ideal for this use case due to its 350ms spin-up time, free tier with no card required, scale-to-zero billing, and Postgres compatibility.
Coding with Lewis·4wWhat a Billion Database Rows Look Like in Real Life
A visual and conceptual exploration of what database scale looks like in physical terms. Starting from 50 rows on a single sheet of paper, the post scales up to a billion rows — equivalent to a two-kilometer-tall stack — and compares that to real-world data volumes from Spotify, Uber, and Facebook. Along the way, it explains core database concepts like indexes and joins using paper-stack analogies, illustrating why Postgres can retrieve a single row from billions in milliseconds. The post is sponsored by Supabase.
Debezium·4wDebezium 3.6.0.Alpha1 Released
Debezium 3.6.0.Alpha1 is the first preview release in the 3.6 cycle, resolving 100 issues across the entire ecosystem. Key highlights include: a new Docling SMT for enriching change events with structured document output suited for AI/RAG workflows; a new Amazon SNS sink for Debezium Server enabling direct CDC fan-out to AWS subscribers; a reworked Oracle LogMiner batch-sizing algorithm based on log file size/count instead of hard-to-tune SCN properties; OpenTelemetry tracing support for the Cassandra connector; OAuth2 authentication and batch mode for the HTTP sink; Agroal replacing C3P0 as the JDBC sink connection pool; and Helm chart improvements for the Debezium Operator and Platform. Breaking changes affect MongoDB (Avro schema name sanitization for collection names starting with digits) and PostgreSQL (enum values now returned in logical sort order rather than storage order).
Let's Get Rusty·5wTop 4 Rust career paths (and which one you should choose)
A breakdown of four main Rust career paths: backend/web services, systems programming/infrastructure, embedded IoT/robotics, and developer tooling. Each path is covered with typical day-to-day work, salary ranges (from ~$100K for mid-level backend to $400K+ for senior systems roles), required skills, and guidance on which path fits different backgrounds. Backend is recommended as the fastest entry point for most developers, while systems programming offers the highest pay but longest ramp-up. The post concludes with a pitch for a structured Rust mentorship program.