You don't need a database, a queue, a distributed system: Go is enough • Hacker News Board

Re: You don't need a database, a queue, a distributed system: Go is enough

#31

Post by sgundo » Mon, Mar 11, 2024, 12:32 PM UTC

gwd wrote: post #11

sgundo wrote: post #5

Earlier quoted context omitted.

I agree it's silly, but sometimes ideas or POCs are silly but worth shipping. Don't you agree?

Worth shipping, but not worth investing massive amounts of time in. On the other hand, suppose you actually hoped to grow and make enough money on something to pay the salary of a few dozen people. Let's say you start with golang and sqlite3, ready to handle 1000s of people an hour, everything is going great, and then someone posts your thing to Hacker News (or it goes viral elsewhere). Suddenly you have millions of…

those are great points. I have read the article about SO and it is inspiring

Re: You don't need a database, a queue, a distributed system: Go is enough

#32

Post by moribvndvs » Mon, Mar 11, 2024, 2:43 PM UTC

vishnugupta wrote: post #9

Title: You don't need a database. Half way down the article: The questions are stored in a sqlite database

> It means that scalability would become an issue if and when Binary Duel is used by more than a few thousands of people an hour. In this fortunate case, I will be very happy to host the infrastructure on a K8 cluster with autoscaling, self-healing, a distributed database, a Redis server and so on.

Re: You don't need a database, a queue, a distributed system: Go is enough

#33

Post by nunez » Mon, Mar 11, 2024, 4:13 PM UTC

yeah...you need all of that if you're writing anything that will be abused by tons of users and handles data in any form.

Re: You don't need a database, a queue, a distributed system: Go is enough

#34

Post by osigurdson » Mon, Mar 11, 2024, 5:54 PM UTC

sgundo wrote: post #28

osigurdson wrote: post #13

If the data in your app doesn't matter at all, and you have no availability requirement, sure keep everything in memory. I don't see what Go has to do with it however, any language should be fine.

golang is very efficient memory wise. And it is easy to develop with. (Rust gods please dont see this)

The author states that scalability doesn't matter here. Any language would have been fine. The title should be "do everything in memory in a single process until you can't ".

Re: You don't need a database, a queue, a distributed system: Go is enough

#35

Post by gwbas1c » Mon, Mar 11, 2024, 6:41 PM UTC

The article should really lead with:

> Let the scalability be a consequence of the success, not something that holds you back.

A large portion of my career was spent fighting the problems that come with "premature scalability."

Re: You don't need a database, a queue, a distributed system: Go is enough

#36

Post by Capricorn2481 » Tue, Mar 12, 2024, 3:39 AM UTC

phyrex wrote: post #6

I don’t disagree with the premise for very small applications, but > The quiz state machine is full in memory > The queue system for the matchmaking is in memory Means those will be nuked as soon as a new version gets uploaded. it really wouldn’t have been much extra work to put this into SQLite as well, and would lead to a much better user experience during updates

Can't you just serialize those things and then migrate them?

Re: You don't need a database, a queue, a distributed system: Go is enough

#37

Post by Capricorn2481 » Tue, Mar 12, 2024, 3:42 AM UTC

Joker_vD wrote: post #22

> We need to choose a database : so, let’s start with that. ...Wait, ten years ago the advice was that this should be one of your last decisions: your application should be able to work with minimal changes with any DBMS, and tying yourself to a specific vendor from the start was considered a bad idea. Did it change while I was not looking?

I don't think these things are incompatible. You can choose a database and still use interfaces to make replacing it possible.