overflow Archives

Tech Optimizer

July 2, 2026

From monolith to Lakebase to LTAP: rethinking the database from storage up

Sixteen years ago, the author began their PhD at UC Berkeley and was advised to focus on analytics rather than OLTP databases, which were considered solved. This led to the creation of Apache Spark and Databricks. However, during the development of Databricks, it was found that OLTP databases were not solved problems; they were difficult to scale and fragile. This realization led to the development of Lakebase, a serverless Postgres database designed with modern technology. Lakebase architecture separates the write-ahead log (WAL) and data files into independent, scalable services. The WAL is externalized to a service called SafeKeeper, which uses Paxos-based replication for durability, while data files are managed by PageServer, which stores them in cloud object storage. This design addresses challenges such as data loss, scaling, and performance interference between transactional and analytical workloads. Lakebase maintains compatibility with Postgres, offers unlimited storage, serverless compute, durable writes, and simpler high availability. It also introduces LTAP (Lake Transactional/Analytical Processing), which allows both transactional and analytical processing to operate on a single data copy in real time, eliminating the need for separate data copies and reducing costs. LTAP utilizes a unified storage layer that allows data to be materialized in both row and columnar formats, optimizing it for both transactional and analytical workloads. The system ensures that analytics can access the most current data without affecting transactional performance by using a log sequence number (LSN) to retrieve the latest changes. Unlike traditional CDC approaches, LTAP requires no explicit table replication, as all data is stored in a single governed copy. This architecture circumvents common issues faced by hybrid transactional/analytical processing (HTAP) systems, such as incomplete feature sets, lack of ecosystem support, and performance contention. The Lakebase architecture has unlocked capabilities like unlimited storage, elastic compute, durable writes, and instant branching, with ongoing developments anticipated in the future.

AppWizard

July 2, 2026

Android’s Linux Terminal no longer restricts you to a single font and window in QPR1 Beta 6

The Android 17 QPR1 Beta 6 has introduced enhancements to the Linux Terminal app, including the ability to import custom fonts from phone storage and multi-window support. Users can now select their preferred font as the default and open new terminal windows via the three-dot overflow menu, with each window appearing in Android’s recents screen. The Linux Terminal app debuted on Pixel devices during the March 2025 Pixel Drop and has seen several improvements since its launch.

Tech Optimizer

July 2, 2026

From monolith to Lakebase to LTAP: rethinking the database from storage up

Sixteen years ago, the author began their PhD at UC Berkeley, where they were advised to focus on analytics rather than OLTP databases, which were considered a solved problem. However, upon developing Databricks, they found that OLTP databases were cumbersome, challenging to scale, and fragile. This led to the creation of Lakebase, a serverless Postgres database designed to address these issues by externalizing the write-ahead log (WAL) and data files into independent services. Lakebase architecture separates the WAL into a distributed service called SafeKeeper and data files into another service called PageServer, allowing for improved durability, scalability, and performance. This architecture eliminates data loss risks associated with disk failures and misconfigurations, simplifies high availability, and allows for elastic compute resources. Lakebase also introduces LTAP (Lake Transactional/Analytical Processing), which enables transactions and analytics to operate on a single data copy in real-time, avoiding the need for separate data copies and reducing costs. The system retains Postgres's ACID semantics while storing data in open columnar formats, making it accessible to both transactional and analytical engines without the delays and complexities of traditional replication methods. The architecture allows for unlimited storage, serverless compute, and instant branching, while ensuring that analytics can read the most current transactional data without affecting transactional workloads. LTAP aims to unify transactional and analytical processing by leveraging distinct compute engines for each workload while integrating at the storage layer.

Winsage

June 23, 2026

Why is Windows 11 so disliked by programmers – and can Microsoft do anything to change things?

Windows is experiencing a decline in favor among developers, with many preferring macOS and Linux for coding. Although nearly half of developers (49.5%) primarily work on Windows, this is often due to organizational mandates rather than personal preference. Developers interviewed did not select Windows as their preferred environment, citing concerns about Microsoft's developer experience, cumbersome tools, and security issues. The Windows Subsystem for Linux (WSL) allows developers to run Linux environments on Windows 11, addressing some compatibility issues. However, there is a consensus that Microsoft should enhance WSL and align Windows more closely with Linux to attract more developers. Critics also point to the intrusive nature of ads and upselling in Windows 11 as detracting from the developer experience.

Winsage

June 11, 2026

Microsoft Patches Record 206 Flaws, Including Three Zero-Days and Critical RCE Bugs

Microsoft announced an update addressing 206 security vulnerabilities, including 39 classified as Critical and 167 as Important. The vulnerabilities include 63 privilege escalation, 56 remote code execution, 30 information disclosure, 27 spoofing, 20 security feature bypass, 7 denial-of-service, and 3 tampering vulnerabilities. Notable critical flaws include CVE-2026-45657 (use-after-free in Windows Kernel, CVSS score 9.8), CVE-2026-47291 (integer overflow in Windows HTTP.sys, CVSS score 9.8), and CVE-2026-44815 (stack-based buffer overflow in Windows DHCP Client, CVSS score 9.8). Microsoft also addressed vulnerabilities related to BitLocker bypass (CVE-2026-45585 and CVE-2026-50507) and introduced a new registry setting to mitigate risks associated with CVE-2026-49160 (denial-of-service vulnerability). The increase in patches is attributed to the use of artificial intelligence in vulnerability discovery, with the current year's reported vulnerabilities surpassing the total from all of 2018.

Tech Optimizer

June 6, 2026

PostgreSQL Dump and Restore: The Complete pg_dump Guide

pg_dump is a utility for exporting a PostgreSQL database into a file, which can be restored on the same or different servers. It exports a single database's tables, views, sequences, functions, indexes, triggers, and in-database grants but does not include roles, tablespaces, or server-level configurations. To capture global objects, pg_dumpall --globals-only should be executed prior to the per-database dump. pg_dump requires CONNECT and SELECT privileges on all tables and sequences within the target database, and a dedicated backup role is sufficient for single-database dumps, while superuser access is needed for global objects. pg_dump supports various output formats: plain SQL (.sql), custom binary (.dump), directory of files, and tar archive (.tar), each with different capabilities for restoration and compression. The custom format allows for selective and parallel restoration. For non-interactive use, credentials can be stored in a .pgpass file or passed via the PGPASSWORD environment variable. Restoration methods depend on the dump format: psql is used for plain SQL files, while pg_restore is used for custom and directory formats. The restoration process requires the target database to be created beforehand. Version mismatches between pg_dump and pg_restore can lead to failures, so it's essential to ensure that the binaries are version-matched. In Docker, pg_dump and pg_restore can be executed within containers, but care must be taken to manage credentials and ensure version compatibility. Exit codes from pg_dump should be checked to confirm successful operations.

Tech Optimizer

June 6, 2026

Azure HorizonDB Enters Public Preview: Web IQ Already Powers Copilot and ChatGPT

Microsoft announced the public preview of Azure HorizonDB, a fully managed PostgreSQL-compatible database designed for agentic AI workloads, during Microsoft Build 2026 in San Francisco. HorizonDB features a "database-as-logs" architecture, allowing for sub-millisecond multi-zone commit latency and independent scaling of compute and storage. It incorporates a Rust-based storage engine, native DiskANN vector search, and in-database AI model invocation. Additionally, Microsoft launched Web IQ, a web-grounding API layer integrated into Microsoft Copilot and OpenAI's ChatGPT, which provides passage-level structured evidence objects rather than full documents. Web IQ is model-agnostic and aims to enhance information density and reduce costs. Both services are currently in limited availability, with HorizonDB open for preview signups across five Azure regions.

Tech Optimizer

June 6, 2026

PostgreSQL vs SQL Server 2026: $0 vs $15K License

PostgreSQL has become the most utilized database for developers for two consecutive years as of 2026, while SQL Server has introduced native AI capabilities and vector search functionalities in its latest release. PostgreSQL is favored for new projects due to its permissive licensing, cross-platform operation, and extensive ecosystem of extensions, whereas SQL Server is preferred by organizations already using Microsoft products for its robust tooling and enterprise support. As of June 2026, SQL Server ranks third in the DB-Engines popularity ranking with a score of 698, while PostgreSQL ranks fourth with a score of 688. Developer adoption trends show that 49% of respondents in the Stack Overflow 2024 Developer Survey use PostgreSQL, compared to 27% for SQL Server. The latest stable version of PostgreSQL is 18.4, released on May 14, 2026, while SQL Server 2025 (version 17.x) became generally available on November 18, 2025. PostgreSQL is free under a permissive license, while SQL Server's Enterprise Edition can cost upwards of ,123 per two-core pack, with an eight-core minimum. PostgreSQL supports various operating systems, including Linux, Windows, macOS, and BSD, while SQL Server operates on Windows and Linux. PostgreSQL uses PL/pgSQL as its primary procedural language, allowing for multiple procedural languages, whereas SQL Server uses T-SQL. PostgreSQL's JSONB type offers rich indexing, while SQL Server added native JSON support in its 2025 release. Both databases are capable of handling high transaction volumes, but PostgreSQL excels in read-heavy scenarios due to its multi-version concurrency control, while SQL Server's columnstore indexes provide advantages for analytical workloads. PostgreSQL supports tables up to 32 TB, while SQL Server can handle a maximum database size of 524 PB. SQL Server's high availability technology includes Always On Availability Groups, while PostgreSQL offers built-in streaming and logical replication. The security features of both databases meet enterprise standards, with PostgreSQL providing a transparent patching process and SQL Server integrating with Microsoft tools. Real-world usage examples include Stack Overflow using SQL Server, while Instagram and Reddit utilize PostgreSQL. Developer sentiment increasingly favors PostgreSQL for new projects, emphasizing flexibility and open-source solutions. For new startups or greenfield projects, PostgreSQL is recommended due to its zero license cost and compatibility. Existing Microsoft enterprises are advised to stick with SQL Server for its integration benefits. Migration from SQL Server to PostgreSQL is becoming common, with a structured approach required for successful transitions.

Winsage

June 3, 2026

Microsoft Brings AI Agents Directly Into the Windows Terminal

Microsoft has released Intelligent Terminal 0.1, an open-source variant of Windows Terminal that includes native agent functionality. It can be installed via the Microsoft Store or WinGet and operates alongside the existing Windows Terminal. Intelligent Terminal allows users to troubleshoot issues directly within the terminal by interacting with an AI agent that understands the terminal context. The tool features a persistent agent pane for seamless interaction, with GitHub Copilot CLI as the default agent, though it supports any ACP-compatible agent. Automatic error detection is included, providing users with relevant error context and potential fixes. An agent management panel helps users oversee multiple agents and their statuses. The Command Palette has been updated to facilitate agent interactions without disrupting the workflow. Microsoft plans to evolve Intelligent Terminal based on community feedback, with its GitHub repository open for contributions. The release also marks the phasing out of Terminal Chat in Windows Terminal Canary, while the mainline Windows Terminal remains unchanged.

Winsage

June 1, 2026

Windows Server vulnerability can grant system privileges with just a malformed packet — domain controllers are being exploited in the wild

Microsoft is facing scrutiny due to a critical remote execution vulnerability, CVE-2026-41089, rated at 9.8, affecting Windows Server domain controllers from version 2012 onward. This vulnerability allows unauthenticated users on the same network to send malformed UDP packets to a domain controller, potentially granting unauthorized system access or causing a reboot, leading to denial-of-service scenarios. The vulnerable service is Netlogon, and there are no immediate mitigations available; patches will be released on May 12. The vulnerability could allow attackers to create multiple accounts with various access levels, compromising the security of entire networks. Cybersecurity experts recommend patching all linked domain controllers simultaneously. The vulnerability is caused by a buffer overflow in the Netlogon service due to a field in a network packet exceeding its expected size. A GitHub repository exists with proof-of-concept code that can crash the LSASS service. Additionally, Microsoft is in conflict with security researcher Chaotic Eclipse, who has published zero-day exploits following a breakdown in negotiations.