Tag
This post discusses the limitations of traditional databases for modern applications and promotes converged databases as a unified solution to handle diverse data types like relational, JSON, and vector data in a single system.
A comprehensive guide to core system design building blocks, including client-server architecture, scaling, and databases, to help with system design problems and interview preparation.
The tweet predicts that the future of software will be shaped by technologies like Postgres, Turbopuffer, Jev, Clickhouse, and open-source LLMs.
This academic paper revisits the dataflow model, likely providing new insights or updates on its theoretical foundations and applications in data management systems.
A technical analysis of Linux 6.6.79 shows that io_uring I/O requests can outlive their submitting process and complete after waitpid() returns, unlike native AIO which waits for drains; the author proposes using exclusive flock locks as a barrier to prevent race conditions during fail-fast recovery.
This article presents vector-bench, a tool designed to benchmark vector indexes across different databases with consistent conditions to accurately measure approximate nearest neighbor search performance.
A PlanetScale engineering post analyzes a MySQL outage caused by a long-running transaction and high concurrency, explaining how parallelism can degrade throughput and how Vitess's transaction pool handled (and amplified) the issue.
PlanetScale describes how it performs massively parallel backups for sharded Postgres databases by spinning up per-shard EC2 instances, restoring prior backups from object storage, and replaying WAL, achieving petabyte-scale backup speeds over 50 GB/s.
A comprehensive argument that PostgreSQL alone is sufficient for most application needs, including caching, search, job queues, and document storage, before reaching for additional specialized systems.
The article argues that ClickHouse has become the dominant database for observability due to its performance handling high-volume, time-ordered logs, solving long-standing log management challenges.
A blog post demonstrating how to use Obsidian Bases to create live, self-updating dashboards from over 20,000 notes by treating the vault as a database and leveraging consistent metadata.
Garry Tan argues that using a database for AI agents is akin to building a Foxconn factory, implying it's insufficient for proper agent functionality.
A tweet highlights a beautiful introduction to Kubernetes and references Fatih Arslan's post on control theory and feedback loops for self-healing, resilient systems capable of scaling thousands of databases.
A comprehensive system design master tree covering fundamentals through real-world applications, including architecture patterns, databases, caching, messaging systems, API design, and deployment strategies. Intended as a structured learning guide for software engineers.
Unicode string equivalence is complex, especially with collations, leading to surprising results like deletion of control characters and non-deterministic grouping. The author discusses challenges in implementing proper Unicode support in database systems.
Maple's service map now automatically shows databases your services are calling, with upcoming integrations for Planetscale, Tinybird, and Clickhouse for more details.
A conversation with Simon (sirupsen) about scaling Shopify, building turbopuffer, and the future of databases, covering engineering principles, AI coding, and hiring practices.
The article analyzes inherent concurrency bugs in SQL, such as atomicity failures, TOCTOU issues, and deadlocks, using a money transfer example to demonstrate correct locking and transaction practices.
An interview with Turing Award winner Mike Stonebraker covering the origins of Postgres, its hardest technical challenges, and his disagreements in the database field.