durability Archives

Tech Optimizer

September 4, 2026

Object Storage + WAL: Lakebase Postgres for the agentic era

Agents interacting with traditional OLTP databases face bottlenecks at the storage layer due to data movement required for operations like deploying instances and managing replicas. Object storage solutions, such as Amazon S3, provide a more efficient and cost-effective alternative. The text discusses two OLTP models: data-centric and transaction-centric. The transaction-centric model emphasizes the importance of transaction history, which Postgres retains through its write-ahead log (WAL). The WAL records every modification before it is committed, allowing for the reconstruction of the database state as of a specific point in time. Lakebase Postgres introduces a two-layer architecture separating compute and storage. The compute layer handles SQL operations, while the storage layer ensures data durability and historical integrity. The WAL is streamed to safekeepers for replication, and the pageserver transforms WAL into materialized pages stored in object storage. This architecture allows for efficient read and write operations without direct interaction with object storage during queries. Key features of Lakebase Postgres include branching, which allows agents to create pointers to specific LSNs without copying data; instant restore capabilities that enable point-in-time recovery; time travel queries for accessing historical data; and read replicas that do not require data duplication. The system also supports scaling down idle compute nodes and eliminates the need for separate copies of data for transactional and analytical processing by storing a single durable copy in object storage. Overall, Lakebase Postgres enhances agent interactions with the database by leveraging object storage as a foundational element.

Tech Optimizer

September 2, 2026

Connecting My LangGraph AI Agent to Postgres

A stateful LangGraph agent was developed to streamline a 15-minute booking process, mimicking a customer service representative. It features a user-friendly Streamlit UI and a backend powered by a Postgres database. The agent can respond to customer queries, calculate service prices, manage acceptance or rejection of services, propose appointment time slots, and confirm booking details. The agent operates in two persistence modes: in-memory for quick testing and Postgres for durability. Testing can be conducted locally with Streamlit or using Docker to simulate a production environment. Docker allows the application to interact with a PostgreSQL server without local installation, enhancing reproducibility. The project includes a docker-compose.yml file to initiate a PostgreSQL container, and users can also utilize a cloud-based Postgres solution. The application behavior remains consistent regardless of the database setup. The complete source code is available on GitHub for testing and further enhancements.

Tech Optimizer

September 1, 2026

Autoscaling Lakebase Postgres

Choosing a database instance size without prior knowledge of the workload can lead to inefficiencies and excessive compute usage. Lakebase Postgres addresses this with an autoscaling feature that eliminates manual sizing, utilizing in-place VM resizing and a monitoring algorithm for CPU, memory, and working set size. Lakebase Postgres separates compute and storage layers, allowing independent resizing of compute nodes without affecting the database. The autoscaling algorithm relies on three signals: CPU load (cpuGoalCU), memory use (memGoalCU), and compute-cache working set size (lfcGoalCU). The CPU load is monitored every five seconds, aiming to maintain it at or below 90% capacity. Memory usage is tracked at two frequencies: overall memory every five seconds and Postgres-specific memory every 100 milliseconds, with a goal to keep usage below 75% of allocated RAM. The compute cache evaluates active data access efficiency, adjusting size based on workload. The working set is estimated using a modified HyperLogLog algorithm that records timestamps for page accesses, allowing for distinct page estimates over various time frames. The algorithm projects future working-set growth to allocate sufficient cache while capping it at 75% of RAM. Resizing the compute involves four components: the autoscaler-agent, vm-monitor, Kubernetes scheduler, and NeonVM. Scaling up occurs when any of the three goals indicate a need for more resources, while scaling down includes verification to ensure sufficient memory remains for operations. Timely adjustments in both directions are prioritized to minimize costs.

Winsage

August 29, 2026

Walmart’s bestselling $799 Windows 11 laptop is now 50% off

Walmart is offering the Sgin 15.6-Inch Windows 11 Laptop at a 50% discount, reducing the price from 9 to 9. The laptop features a 15.6-inch full HD display (1920 x 1080), an AMD Ryzen 5 3500U Quad Core Processor, 16GB of DDR4 RAM, and a 512GB solid-state drive (SSD). It runs on Windows 11, which includes security features like Microsoft Defender and facial recognition through Windows Hello. The laptop has a battery life of up to six hours and is noted for its multitasking capabilities, quiet cooling fan, and lightweight design. However, it lacks expandable storage options and may still be considered pricey by some consumers.

Tech Optimizer

August 29, 2026

Databricks Unveils Lakebase Postgres

Lakebase Postgres features a two-layer architecture that separates operations for durability and scalability. The compute layer uses standard Postgres for SQL parsing, query planning, and execution, designed to be ephemeral for dynamic scaling. The storage layer ensures correctness, durability, and historical accuracy, consisting of three components: Safekeepers replicate Write-Ahead Logging (WAL) records using a quorum-based protocol; Pageserver transforms WAL records into page versions; and Object Storage retains materialized versions and historical states in an immutable format. This architecture enhances data durability and system scalability.

Tech Optimizer

August 25, 2026

Migrate Vaultwarden to PostgreSQL: Scale for Teams [2026]

Self-hosting Vaultwarden with SQLite can lead to performance issues as the user base grows, particularly due to SQLite's limitations with concurrent writes. Transitioning to PostgreSQL allows for better performance, multi-user support, and enhanced data durability. PostgreSQL supports concurrent connections and row-level locking, making it more suitable for team environments. To migrate from SQLite to PostgreSQL, certain prerequisites must be met, including having an existing Vaultwarden deployment, Docker Engine, a PostgreSQL server, and pgloader installed. The migration process involves backing up existing data, deploying a PostgreSQL container, updating configuration files, and using pgloader to transfer data. A VPS with 2 vCPU and 4GB RAM can support up to 50 users, with larger teams requiring more resources. PostgreSQL also allows for the creation of organizations for shared vault access and the configuration of group policies for security. Regular backups and performance tuning are necessary to maintain optimal operation. Common pitfalls during migration include not stopping the Vaultwarden container before migration, failing to encode special characters in the database password, and neglecting to back up data. Troubleshooting may involve checking connection strings and ensuring the PostgreSQL container is healthy. Advanced configurations can enhance performance and functionality, and understanding the differences between Vaultwarden and Bitwarden's official self-hosted server can aid in decision-making.

Tech Optimizer

August 18, 2026

Migrate Amazon Aurora PostgreSQL across major versions with active Debezium CDC connectors using native logical replication

Organizations using Debezium Change Data Capture (CDC) connectors on Amazon Aurora PostgreSQL-Compatible Edition face challenges during major database version upgrades. In-place upgrades require downtime, while blue/green deployments disrupt CDC event pipelines. A method using PostgreSQL's native logical replication allows migration between a source cluster (current version) and a target cluster (new major version) without a full connector re-snapshot. This approach minimizes risks of data loss and allows existing Debezium connectors to operate on the source during synchronization. The cutover process involves disabling the replication subscription, synchronizing sequences, creating a new Debezium replication slot on the target, and redirecting the connector, resulting in a brief pause for Kafka consumers. Prerequisites for this method include enabling logical replication on the source cluster, ensuring the target cluster is provisioned in the same VPC, and confirming that tables participating in CDC have primary keys. The process involves configuring parameter groups, creating publications, and establishing subscriptions for logical replication. During cutover, application writes are halted, and replication lag must be monitored to ensure it reaches zero before proceeding. After the cutover, ongoing monitoring of replication health and Kafka consumer offsets is necessary. Common failure scenarios include Aurora writer failover, Debezium connector stalls, large messages exceeding Kafka limits, DDL changes during synchronization, and long-running transactions blocking lag drain. Each scenario has specific symptoms, detection methods, and resolutions. Post-migration, organizations should establish monitoring for replication lag growth and Kafka consumer offset divergence. Automation can streamline the migration process for organizations managing multiple clusters, utilizing AWS Cloud Development Kit (CDK) constructs for cluster provisioning, schema replication, and cutover orchestration. After verifying stable operation on the target cluster, the old Debezium connector and source cluster can be decommissioned. Limitations include the absence of failover slots on Aurora PostgreSQL 17 and the need to handle TOAST columns appropriately.

Winsage

August 14, 2026

One of our favorite Snapdragon X Plus Surface Laptops just dropped 27% — finally making it affordable again

In April, Microsoft increased the prices of its Surface laptops due to the RAM crisis, making them less accessible for consumers. However, discounts are available, such as a 27% reduction on the Microsoft Surface Laptop (7th Edition) at Best Buy, bringing its price to ,099.99. The laptop features a Snapdragon X Plus CPU, a 13.8-inch 2K touchscreen display with a 120Hz refresh rate, 16GB of RAM, and a 512GB SSD. It offers impressive battery life of 18-19 hours and includes a Neural Processing Unit (NPU) for AI applications. The device is suitable for professional and academic tasks and is noted for its durability and portability.

Winsage

July 30, 2026

ThinkPads from 2008 are some of the hottest used laptops right now — Here’s how (and why) they’re being turned into Windows 11 PCs

The ThinkPad X210Ai is a modified laptop that combines the chassis of older ThinkPad models (X200/X201) with a modern mainboard from TP Art, featuring Intel Core Ultra processors, DDR5 RAM support, dual M.2 SSD slots, Thunderbolt 4, and HDMI 2.1. The modification allows users to retain the original display and keyboard while requiring some chassis adjustments. TP Art offers a kit starting at 9, with complete builds beginning at 9, excluding RAM and storage. The popularity of the X210Ai has surged due to rising RAM prices and the demand for reliable, customizable machines. The modified board allows compatibility with Windows 11 and various Linux distributions. Processing times for orders can take up to six months, and cancellations are not allowed once placed.

Tech Optimizer

July 12, 2026

What Is Serverless PostgreSQL?

Serverless PostgreSQL is a fully managed cloud database model that separates compute and storage, allowing them to scale independently and automatically based on demand. It eliminates the need for manual infrastructure provisioning and capacity planning, charging only for active usage. Unlike traditional PostgreSQL setups, which require continuous resource allocation and manual scaling, serverless PostgreSQL provisions resources on demand and can scale down to zero during idle periods. Serverless PostgreSQL integrates with serverless compute platforms, enabling analytical queries to access the same data within a unified architecture. Key differences between traditional and serverless PostgreSQL include manual versus automatic provisioning and scaling, fixed versus usage-based billing, and high versus reduced operational overhead. Lakebase architecture is an emerging model that combines transactional databases with lakehouse foundations, allowing operational and analytical workloads to coexist on a single platform. This architecture minimizes data duplication and simplifies access, enhancing data management and analysis. Serverless PostgreSQL operates on a cloud-native architecture that enhances efficiency by allowing compute and storage to scale autonomously. It features scale-to-zero behavior, where compute resources are suspended when inactive and reactivated upon new queries. Major providers include Databricks Lakebase, Amazon Aurora Serverless v2, and Neon, each offering varying capabilities and integrations. Pricing for serverless PostgreSQL typically includes charges for compute resources, storage, and data transfer, with costs fluctuating based on workload activity. Cold start latency is a performance consideration, as reactivating compute resources can introduce delays. Strategies to mitigate this include keeping resources partially active or selecting providers with minimal cold start impacts. Serverless PostgreSQL is well-suited for OLTP workloads, while lakebase architecture is better for AI development, variable workloads, and environments requiring rapid iteration. Setting up serverless PostgreSQL involves choosing a provider, creating a database instance, and configuring access settings. It can also be used alongside serverless compute platforms for analytics, further extending its capabilities.