https://hypercrux.com/tags/multi-model-databases/ Recent content in Multi-Model Databases on HyperCrux.com Hugo en-us Tue, 06 Oct 2026 00:00:00 +0000 https://hypercrux.com/one-sqlite-file-instead-of-three-databases-hypercrux-0.1-keeps-records-links-and-vectors-together/ Tue, 06 Oct 2026 00:00:00 +0000 https://hypercrux.com/one-sqlite-file-instead-of-three-databases-hypercrux-0.1-keeps-records-links-and-vectors-together/ <p>Add search by meaning to an app and the data splits in three. The records stay in the regular database. Their embeddings go to a vector database, so the app can find documents that are about the same thing as a question. The connections between records, who owns what and which document cites which, end up in a graph database or a join table nobody likes. Then something has to copy every change from one to the others, and the day it misses one, a search returns a document that was deleted last week.</p> https://hypercrux.com/what-is-a-multi-model-database-keys-sql-graphs-and-vectors-explained/ Tue, 06 Oct 2026 00:00:00 +0000 https://hypercrux.com/what-is-a-multi-model-database-keys-sql-graphs-and-vectors-explained/ <p>A database is a way of keeping facts so you can find them again. The catch is that &ldquo;find&rdquo; means different things. Sometimes you know exactly which record you want. Sometimes you want every record that matches a condition. Sometimes you want whatever is connected to something you already have, or whatever means roughly the same as a sentence you just typed. Each of those questions has a shape of database built around it.</p>