Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A database for 2022

tailscale.com

Post reply on HN
Print view View original

201–210 of 336 posts

Re: A database for 2022

#201

Post by bob1029 »

This is great. We've been using sqlite in production as our exclusive database storage solution for over half a decade. For non-trivial, multi-user systems too.

Replication of data has always been a concern for us, with the current mitigation being periodic VM snapshots. In order to engage larger customers, we would need to tighten this up.

Our next gen data storage technology leverages some dark magic from fintech. Append-only log, single writer, synchronous replication, etc. Most recent benchmarks with replication to 1 sync witness on same lan are in excess of 200k business objects created or updated per second.

Re: A database for 2022

#202

Post by pooper »

Operyl wrote: post #186
Issaclabs wrote: post #184

Earlier quoted context omitted.

What does that mean? Can you explain?

This comment trivializing Dropbox: https://news.ycombinator.com/item?id=9224

I for one do not think the comments trivialized anything. I see these as inevitable questions that a leader like Drew Houston should be prepared to answer at some point. Think of it this way, would you disqualify me if you were hiring and I asked a similar question at the interview?

I think the underlying actual question for Dropbox to ponder (but perhaps not answer publicly) was "what is your moat?" without the business development language and at least for me that remains an open question.

I remember I was in college when Dropbox started and I thought Dropbox was silly to offer more storage for inviting more users. It was easy to approach people and ask them to try something in college. I think I almost maxed out my invites. I remember feeling I was taking Dropbox to the cleaners...

One activity question for HN: why do you think Dropbox continues to exist today while copycats like Barracuda Copy have failed?

Re: A database for 2022

#204

Post by [deleted] »

dastbe wrote: post #108
tptacek wrote: post #87

This thread has (at least at the moment) serious Bob Martin Sudoku Solver energy to it. Tailscale has solved an infamously complicated problem using, for the most part, simple tools. They're not just successful; they're remarkably successful, spookily successful, upsettingly successful. Consider whether the secret sauce here might not be au courant database choices, but rather something much harder for random teams t…

nobody goes to these restaurants for their omelets, though at the same time nobody should care how tailscale actually implements things so long as it works well. imo they’re not solving a notoriously hard problem, they’re realizing that they have the tiniest version of this problem (and that will most likely continue to be true). when that’s the case and you want to prioritize stuff that moves the needle like dev vel…

[deleted]

Re: A database for 2022

#205

Post by mettamage »

rablackburn wrote: post #100

I loved this article, despite the negativity. A discussion that keeps recurring on HN is how you can get a lot done with simple, boring solutions. This is a perfect example of that in practice. What’s the simplest thing that’ll work? Do that, monitor the solution, and when you start hitting a limitation reevaluate what the next appropriate solution is. There are plenty of comments here deriding this as insanity when…

I favorited your post. It has taken out some insecurities that I had about best practices. I couldn't explicitly formulate them either. Thanks for the (professional/career) advice/therapy :)

Re: A database for 2022

#206

Post by [deleted] »

rablackburn wrote: post #100

I loved this article, despite the negativity. A discussion that keeps recurring on HN is how you can get a lot done with simple, boring solutions. This is a perfect example of that in practice. What’s the simplest thing that’ll work? Do that, monitor the solution, and when you start hitting a limitation reevaluate what the next appropriate solution is. There are plenty of comments here deriding this as insanity when…

[deleted]

Re: A database for 2022

#207

Post by jitl »

endisneigh wrote: post #7

I'm so desperate for a SQL database where I can just put it on a bunch of commodity hardware via Docker, connect them up and never worry about this again. Ideally it'd monitor my queries and create indexes for me. pleeeeeeaaaaaaaaaaaassssseeeeeeeeee /dream FoundationDB is similar but you have to do so much yourself. It's more or less what I'm describing for a key value store though. Not sure why it's not more popular…

I am hoping EdgeDB heads this direction to some extent.

Re: A database for 2022

#208

Post by billywhizz »

AnimalMuppet wrote: post #161
billywhizz wrote: post #150

Earlier quoted context omitted.

oh boy. is nobody allowed to make a little joke anymore. you should take yourself a lot less seriously my dude.

First: I am not "my dude" to you. And, completely apart from the database, it's a really valid point - not a joke at all. When someone says, "It's 2022. Why are we still arguing about X?" or some such, it means that they haven't been able to persuade the rest of the world about X on the merits of their argument, and so they want to short-circuit the argument by appearing "modern" or "up to date" or "on the right side…

No post body was provided.

Re: A database for 2022

#209

Post by alophawen »

Not commenting on tailscale, but for the state of databases.

Sometimes boring is the right choice. PostgreSQL has worked for decades now, and seems to have regained much of the performance that MySQL once boasted.

If you do this for the money, investing in tried and true (but boring) software should be the default solution.

I watched with dread how the MongoDB fiasco played out a decade ago. Meanwhile, I kept using PostgreSQL and had a good ride.

Post reply on HN