Skip to content

Database

Lauri Ojansivu edited this page Mar 20, 2026 · 89 revisions

AI

Agent

Cache

MCP

ORM

Turso

Zero downtime migrations at petabyte scale (2024)

Data Processing Benchmark Featuring Rust, Go, Swift, Zig, Julia etc.

Databases in 2025: A Year in Review

Git Branching style for data

MongoDB

Positron – A next-generation data science IDE

RaptorCast: Designing a Messaging Layer

Cleanup

Realtime

DSL

Wrong ways to use the databases, when the pendulum swung too far

TigerBeetle

Show HN: NanoTS – Fast, embeddable, tiny time series database

Aurora

Show HN: Defuddle, an HTML-to-Markdown alternative to Readability

TLA+

Fast, Simple and Open Firebase Alternative: TrailBase

Anonymization

CSV

JQ

Data

DuckDB

File

JSON

YAML

SpacetimeDB

SQL

FerretDB

PostgreSQL

Microsoft SQL Server

Graph database

CockroachDB

Litestream

Livestore

  • LiveStore: State management based on reactive SQLite and built-in sync engine
  • From Prisma Founder to LiveStore: Building local-first apps with Johannes Schickling
    • https://www.youtube.com/watch?v=aKTbGIrkrLE
    • LiveStore voi synkata selaimen tabit myös offline? Broadcast channel, give name to it to post, to cross-tabs. Or localstorage. Or indexDB. Or shared worker, used at LiveStore
    • LiveStore can sync browser tabs also offline. Ways:
      • Use shared worker, this is what LiveStore uses. Other ways would be:
      • Add broadcast channel, give name to it, post to cross-tabs
      • Use localstorage from all tabs
      • Use IndexDB
    • Pull or push requests for events since time something, or rebase. Just persist event log to D1, turso, postgres, elsewhere.
    • Store can be CloudFlare Workers, using web sockets get realtime feedback, receives events, lets everyone know. Replicache is similar architecture.
    • LocalFirstFM podcast has more info

SQLite

Valkey Turns One: Community fork of Redis

Vector

XML

Clone this wiki locally