Building a highly-available web service without a database
blog.screenshotbot.io
Building a highly-available web service without a database
1–10 of 187 posts
Re: Building a highly-available web service without a database
#2[deleted]
Re: Building a highly-available web service without a database
#3[flagged]
Re: Building a highly-available web service without a database
#4We didn’t want to build something complicated, so we implemented our own raft consensus layer. Have you considered just using Redis?
Re: Building a highly-available web service without a database
#5We didn’t want to build something complicated, so we implemented our own raft consensus layer. Have you considered just using Redis?
Haha, I totally hear you. But but, we didn't really build the raft consensus layer from scratch. We used an existing robust library for that: https://github.com/baidu/braft
Re: Building a highly-available web service without a database
#6We didn’t want to build something complicated, so we implemented our own raft consensus layer. Have you considered just using Redis?
Haha, I totally hear you. But but, we didn't really build the raft consensus layer from scratch. We used an existing robust library for that: https://github.com/baidu/braft
[deleted]
Re: Building a highly-available web service without a database
#7I would use cloudflare R2 but its not globally distributed so its pointless using it on edge
otherwise I get the messaging with edge you the database is the bottleneck
just need a one stop shop to do edge functions + edge db
Re: Building a highly-available web service without a database
#8Decades ago, PG wrote that he didn't use a database for Viaweb, and that it seemed odd for web apps to be frontends to databases when desktop apps were not[0]. HN also doesn't use a database.
That's no longer true, with modern desktop and mobile apps often using a database (usually SQLite) because relational data storage and queries turn out to be pretty useful in a wide range of applications.
Re: Building a highly-available web service without a database
#9Not sure I would call that setup simple, but it is interesting. I have honestly never heard of ‘Raft’ or the Raft Consensus Protocol or bknr.datastore, so always happy to learn something on a Friday night.
Re: Building a highly-available web service without a database
#10Not sure I would call that setup simple, but it is interesting. I have honestly never heard of ‘Raft’ or the Raft Consensus Protocol or bknr.datastore, so always happy to learn something on a Friday night.
Author here.
I agree, the infrastructure required to make this happen eventually gets quite complicated. But the developer experience is what's super simple. If somebody had to take all our infrastructure and just use it to build their next big app, they can get the simplicity without worrying about the internal plumbing.