Databases

1. DB   db

ID: a833eb98-c31e-4492-ac07-e718a9bce086
CREATED: <2025-02-16 Sun 19:06>

[2025-02-16 Sun 19:06] Database - Wikipedia

1.1. Partition

ID: f239f934-a477-4050-8d19-3c2597a64b34
CREATED: <2025-02-16 Sun 19:07>

[2025-02-16 Sun 19:08] Partition (database) - Wikipedia

1.1.1. Shard

ID: 03aa2c81-5318-45d7-853f-bbcfdb8e7d48
CREATED: <2025-02-16 Sun 19:07>

[2025-02-16 Sun 19:07] Shard (database architecture) - Wikipedia

1.2. Spatial Database

ID: 999c2245-1e81-49c5-a0a4-6ba4d18ee132
CREATED: <2025-05-07 Wed 17:44>

[2025-05-07 Wed 17:45] wiki

1.3. Moving Object Database

ID: 7f41f3ea-fd20-410a-9dc8-be188220a382
AKA: MOD
CREATED: <2025-05-07 Wed 17:41>

Moving Object Database https://web.archive.org/web/20110611054912/http://www.comp.nus.edu.sg/~chensu/sigmod08.pdf

1.4. DBMS   dbms

ID: 3bd5f5f8-956b-49a4-b280-eec4a8c0f85e
CREATED: <2025-02-16 Sun 19:09>

[2025-02-16 Sun 19:16] IBM Documentation

Database Management Systems

Traditionally DBMS has referred to a large, closed system. This paradigm is slowly diminishing as we move towards more capable middleware and micro-service architectures which defeat the purpose of a monolithic, weakly distributed system.

Our understanding of DBMS, for the purpose of this node is quite vague - it is anything which is powerful enough to be used as the core of a DBMS on its own or which covers enough surface area in the DB school of thought to be considered one.

1.4.1. RocksDB   rocksdb

ID: b569a646-de4c-4287-8599-52b237a753b4
CREATED: <2025-02-27 Thu 16:17>

[2025-04-15 Tue 15:04] <- LSM Tree

  • Dragon: A distributed graph query engine - Engineering at Meta

    • describes usage of TAO

    Dragon is backed by a demand-filled, in-process key-value store, updated in real time and eventually consistent. It uses a number of optimization techniques to conserve storage, improve locality, and execute queries in 1 ms or 2 ms with high availability and consistency.

    Even though some of the ideas have been around for a while, Dragon combines them at scale and in novel ways to push down many complex queries closer to storage. It’s structured more as a distributed database engine that retrieves the requested results as efficiently as possible along with any ranking signals stored in the index. This allows applications to focus on business logic, privacy, static type checking, and sophisticated ranking systems instead of spending a lot of time worrying about the best way to retrieve graph data.

    (->> ($alice) (assoc $friends) (assoc $friends) (filter (> age 20)) (count))

    (->> ($me) (assoc $groups)
      (->> (assoc $members) (count))
      (orderby (count))
        (limit $count $offset))
    

1.4.2. DataFusion   apache

ID: 3ce0b887-31ea-4a78-96a2-6671907a687a
CREATED: <2025-02-16 Sun 19:09>

[2025-02-16 Sun 19:16] Apache DataFusion — Apache DataFusion documentation

  1. Arrow
    ID: dd24ce27-3907-48e4-8b5d-8be8b2035ae1
    CREATED: <2025-02-27 Thu 18:02>
    

    [2025-02-27 Thu 18:02] Apache Arrow | Apache Arrow

1.4.3. tigerbeetle   fin zig

ID: 9933d695-6379-4903-a4d5-0aa887bfa7d9
CREATED: <2025-02-27 Thu 16:17>

[2025-02-27 Thu 16:17] GitHub - tigerbeetle/tigerbeetle: The financial transactions database designed for mission critical safety and performance.

  • very high quality code
  • zig
  • excellent style guide