Show HN: WunderBase – Serverless OSS Database on Top of SQLite, Firecracker

• litestream

  165 9,933 7.5 Go

  Streaming replication for SQLite.

As discussed in the post, the next steps are to add read replicas. Regarding backups, that's possible with Litestream: https://github.com/benbjohnson/litestream

• litefs

  38 3,596 8.0 Go

  FUSE-based file system for replicating SQLite databases across a cluster of machines

  

Are you going to use LiteFS then for replication? https://github.com/superfly/litefs

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• sqlite-s3vfs

  3 112 4.6 Python

  Python writable virtual filesystem for SQLite on S3

  

• prisma-engines

  10 1,092 9.7 Rust

  🚂 Engine components of Prisma ORM

  

• pocketbase

  176 33,003 9.7 Go

  Open Source realtime backend in 1 file

  

pocketbase is great, I used it in several personal projects, and I really like it

https://github.com/pocketbase/pocketbase

PocketBase is an open source Go backend, consisting of:

  * embedded database (SQLite) with realtime subscriptions

• prisma1

  64 16,816 5.1 Scala

  Discontinued 💾 Database Tools incl. ORM, Migrations and Admin UI (Postgres, MySQL & MongoDB) [deprecated]

  

Hey there, I'm Nikolas from the Prisma team. Just came here to quickly clarify this notion:

> Prisma is an API server that puts a GraphQL API in front of a DB.

Prisma is an ORM which generates a JavaScript/TypeScript client library for your database.

Your description is very true for Prisma 1 (which has been in maintenance mode for several years and is officially deprecated by now [1]), but the latest version(s) of Prisma (v2+) don't expose a GraphQL API any more. Prisma 1 also used GraphQL SDL for data modeling, the Prisma ORM on the other hand has its own, custom modeling language for describing database schemas in a declarative way and also comes with a flexible migration system.

That being said (and as Jens also mentioned elsewhere), the Prisma ORM does use GraphQL _internally_ as a wire protocol. However, as a developer, you _never_ touch this internal GraphQL layer and are not even supposed to be aware of it (you actually have to jump through a lot of hoops to even "find" it). It's also very likely that we'll replace GraphQL as a wire protocol in the future, so "GraphQL" really isn't something you should be thinking about as a developer who is using Prisma.

Hope that clarifies the situation a bit, let me know if you have any further questions around this topic.

[1] https://github.com/prisma/prisma1/issues/5208

Suggest a related project