klotz: database* + production engineering*

0 bookmark(s) - Sort by: Date ↓ / Title / - Bookmarks from other users for this tag

  1. The article explores a real-world architectural shift where specialized data tools—Redis for caching/pub-sub, Elasticsearch for search, and Kafka for event streaming—were consolidated into a single database engine: PostgreSQL. The primary motivation was to reduce operational complexity, simplify the infrastructure stack, and minimize the cognitive load on developers by managing one unified system instead of several distributed ones.
    Summary points:
    - Consolidating specialized tools into PostgreSQL reduces overhead in deployment, monitoring, and data synchronization.
    - Modern Postgres features like GIN indexes and Full Text Search can effectively substitute for Elasticsearch in many use cases.
    - Utilizing Postgres's LISTEN/NOTIFY or simple table structures can replace lightweight pub-sub needs previously handled by Redis or Kafka.
  2. An account of how a developer, Alexey Grigorev, accidentally deleted 2.5 years of data from his AI Shipping Labs and DataTalks.Club websites using Claude Code and Terraform. Grigorev intended to migrate his website to AWS, but a missing state file and subsequent actions by Claude Code led to a complete wipe of the production setup, including the database and snapshots. The data was ultimately restored with help from Amazon Business support. The article highlights the importance of backups, careful permissions management, and manual review of potentially destructive actions performed by AI agents.
  3. This tutorial provides a comprehensive guide to Apache Doris, a high-performance, real-time analytical database. It covers installation, basic operations, data loading, querying, and performance optimization.

Top of the page

First / Previous / Next / Last / Page 1 of 0 SemanticScuttle - klotz.me: Tags: database + production engineering

About - Propulsed by SemanticScuttle