WunderBase
Data
serverless database
SHOW HN2022
179points
47comments
#332of 2,570 in 2022
Top 13%of 2022 by points
How HN took it
CuriousMostly questions and neutral comments
3 positive, 11 neutral or asking, 0 mixed, 8 critical, out of 22 comments about the project. Thread score -0.24.
Idea: 3 for, 1 againstExecution: 0 for, 2 againstDesign: 0 for, 2 againstPrivacy: 0 for, 2 againstPerformance: 0 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Interesting idea for scaling lower-cost dev databases
From 1 comment
This just runs a request proxy that turns off after 10 seconds of no activity and starts it up (with a half second delay) when there is a new request. It runs SQLite with Prisma.…
gregwebs on HN
Serverless database concept is appealing
From 1 comment
Serverless database. Loving it! Good-luck!
talhof8 on HN
Objections
Scales only between 0 and 1 instance, not truly serverless
From 2 comments
This just runs a request proxy that turns off after 10 seconds of no activity and starts it up (with a half second delay) when there is a new request. It runs SQLite with Prisma.…
gregwebs on HNI was pretty interested to see how this worked as well. I think you are right, this is a toy. It will be interesting to see if they can solve scaling. It would be cool if you…
lbhdc on HN
Not reliable for production; replication is asynchronous and can lose data
From 2 comments
This just runs a request proxy that turns off after 10 seconds of no activity and starts it up (with a half second delay) when there is a new request. It runs SQLite with Prisma.…
gregwebs on HNAre you going to use LiteFS then for replication [1]? LiteFS replication is asynchronous, meaning failover can lose the latest data. Will LiteFS scale down to 0? Does scaling…
gregwebs on HN
Cold start delay and proxy startup time seem high
From 1 comment
500ms seems high for a cold start for a proxy layer. Is there anything I’m missing? JVM is pretty awful at cold starts but with graalvm I got a pretty big micronaut project…
mrhands556 on HN
Exposing the database publicly is a security risk
From 2 comments
>I do not recommend to expose WunderBase to the public internet. The intended use case is to run it on a private network and expose it to your frontend via an API Gateway, like…
bragr on HNSeeing how many MongoDB instances were running wide open to the internet despite calls to not do so, your concern is certainly valid.
shabbatt on HN
Requests
Drop the GraphQL layer and allow a standard SQLite client
From 1 comment
I was pretty interested to see how this worked as well. I think you are right, this is a toy. It will be interesting to see if they can solve scaling. It would be cool if you…
lbhdc on HN
Add read replicas and backups
From 1 comment
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
jensneuse on HN
Questions
How is replication and scaling handled across instances?
From 2 comments
You can, of course, scale to >1 with the Fly Machines API. I don't know enough about how they're managing the SQLite part of this to say more about how this scales, except that I…
tptacek on HNhmm but how would the replication and sync be handled if you have many sqlite instances on edge locations around the world? If someone inserts a row with id 234 and somebody from…
shabbatt on HN
Will LiteFS scale to zero and how fast is failover?
From 2 comments
Are you going to use LiteFS then for replication [1]? LiteFS replication is asynchronous, meaning failover can lose the latest data. Will LiteFS scale down to 0? Does scaling…
gregwebs on HNLiteFS/Litestream author here. LiteFS will scale to zero with a persistent volume attached. For short-lived instances (aka serverless), we still have a few more features to…
benbjohnson on HN
Alternatives named
Fly.io Postgres and LiteFS
From 2 comments
Yes: the model topology you should have in your head is "single writer, multiple readers" --- exactly the same way it would work with a conventional Postgres setup. What you're…
tptacek on HNAre you going to use LiteFS then for replication [1]? LiteFS replication is asynchronous, meaning failover can lose the latest data. Will LiteFS scale down to 0? Does scaling…
gregwebs on HN
Aurora Serverless v2
From 2 comments
For many fly.io is not a viable alternative especially those that are already on the AWS train. I think that AWS already offers Aurora Serverless v2 which pretty much…
shabbatt on HN> I think that AWS already offers Aurora Serverless v2 which pretty much accomplishes what a lot of these me-too-serverless services that won't integrate as well as something…
vosper on HN
PocketBase
From 1 comment
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:…
pqyzwbq on HN
rqlite
From 1 comment
I'm mostly interested in the SQLite part of this, and we don't have an SQLite offering, only Postgres, just to be clear. So you can't hurt my feelings here. When does SQLite…
tptacek on HN