sgundo's comments

On: Doom in K8s

[sgundo]

An expensive way to run Doom.

On: Ask HK: I would like to re-learn C. Any suggestions for a weekend project?

[sgundo]

do you have any blog to suggest for an implementation?

[mytailorisrich → sgundo]

If you're interested in the topic there is the aptly-named "Raytracing in one weekend" series of free books:

https://raytracing.github.io/

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

[sgundo]

golang is very efficient memory wise. And it is easy to develop with.

(Rust gods please dont see this)

[osigurdson → sgundo]

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 ".

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

[sgundo]

great to hear!

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

[sgundo]

I am gonna be honest, I was laughing writing that part! :)

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

[sgundo]

Yeah, it is kind of provocatory. Of course you can't build a business out of an in-memory game, but it is fun to ship something as it is. Without thinking too much about scalability.

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

[sgundo]

You are right, but i can roll updates during the night without causing any issue. Since after you finished playing you don't have a way to access your old games anymore

[9dev → sgundo]

That works for the specific case presented here. As soon as you have users from other timezones, ”during the night“ becomes a really complicated concept quickly.

[sgundo → 9dev]

you are definetely right. :)

[jstanley → sgundo]

> i can roll updates during the night without causing any issue

This isn't universally true.

I work on a telephony platform, some components of which need to be upgraded very carefully, because if you just restart the daemon without first transferring load elsewhere then you drop people's calls.

OK, there are less calls at night time, but there are calls all of the time and people don't expect their calls to randomly drop just because it's night time.

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

[sgundo]

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

[gwd → sgundo]

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 eyeballs an hour, of whom your non-scalable infrastructure turns away 99.9%. What's the chance you get another shot after you've re-architected everything to be more scalable?

I don't have a good idea how likely that is; at some point I seem to recall hearing that Stack Overflow was run on just two servers, made possible because it was just efficient. But it's certainly something to take into consideration if you're hoping to grow large; and only something to ignore if you don't really care.

[sgundo → gwd]

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

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

[sgundo]

This article is a reminder to me and you all that you probably don’t need to make things harder for yourself.

On: Show HN: Binary Duel. A quiz game to show who's the real 10x

[sgundo]

thanks a lot! Do you mean something like a shareable message?