Guides
Architecture guides, decision trees, and real-world examples for building with multiple databases.
Most production apps use more than one database. Here's what that means, why it happens, and how to think about it.
→A practical decision guide for choosing the right database combination based on what your application actually needs — not what's trendy.
→How to add Redis to an existing PostgreSQL application, when it makes sense, and the cache-aside pattern that most production apps use.
→Full-text search is a solved problem — but not by PostgreSQL. Here's when Elasticsearch becomes necessary and how to wire it up alongside your existing database.
→Every AI-powered application needs at least three databases. Here's the architecture that works, why vector databases exist, and how to combine them with your existing stack.
→