Relational & NoSQL databases, search, caches, streams, ETL/ELT, and analytics stacks.
An article joins this feed when it matches these terms. Each one is also a search of its own.
The difficult part of search isn't finding a word. It's returning the right results quickly while documents change, users type, and parts of the search infrastructure fail. Imagine an e-commerce catalog with millions of products. A user types iph, sees…
At 10:00 a.m., tickets for a popular concert go on sale. Thousands of customers refresh the same seat map. Two people click the same front-row seat almost simultaneously. Both see it as available. Both press Reserve. Only one of them can own…
Author: Tobie Morgan Hitchcock AI agents have a memory problem: most of what they know lives either in the current context window, in local siloed memory solutions, or in an external retrieval system. That works up to a point. But…
Author: Tobie Morgan Hitchcock SurrealKV 1.0 is a new open source persistent storage engine for SurrealDB, written in Rust and released under Apache 2.0 on 13 October 2026. With synchronous durability, it reads 7.95× faster than RocksDB and 73.7× faster than SlateDB, and it will be…
Spinning up a database used to mean planning hardware, installing software, and configuring backups. With Oracle Autonomous AI Database on OCI, you can have a working database in minutes. The step that trips most people up isn't creating it, though.
CedroDB is an experimental open-source project exploring another approach: combining several of these capabilities into a single local-first storage engine written in Rust. The project provides native libraries for Python and Node.js/TypeScript, allowing developers to interact with the…
XAMPP's MySQL refused to start, so you followed the usual advice and copied C:\xampp\mysql\backup over C:\xampp\mysql\data, or reinstalled XAMPP and copied your old database folder across. MySQL starts again, your shop_db database shows its tables in the…
A MySQL deadlock report shows a query ID, but you can't find the SQL statement that caused the problem. You have the thread ID and query ID from SHOW ENGINE INNODB STATUS, yet neither tells you directly what was executed.
java.sql.SQLException: Unknown character set index for field '255' received from server. If your app suddenly throws this after moving to MySQL 8, the database isn't broken. Your client is too old to understand the collation the server is sending back.
If your app shows "new row violates row-level security policy for table" (Postgres code 42501), the short answer: Postgres refused the row because no policy's WITH CHECK allows it for the role making the request. Add an INSERT policy (and UPDATE…