I wouldn't call that a monolith then.
Well if you're distributing requests over multiple servers, I wouldn't call that a monolith.
Wait, so in what sense is it a monolith then? :D
Can you do concurrent reads to a disk? I actually don't know the answer to this. I'm pretty sure you can't on an HDD, but I don't know about an SSD.
> they went over how they handle a billion requests a day with mostly a Rails monolith 1 day has 246060=86400 seconds. 1bn/86400 is more than 10000 reqs/second, so each request has to be served in less than 100 us.…
That sounds specific to where you live. In London the buses are amazing.
Unrelated to git, but I LOVE how fast and user-friendly this page is.
This is yet another instance of a phenomenon: When you have good outcomes and bad outcomes, and you take some preventative measures to reduce the likelihood of bad outcomes, as time goes by people start believing that…
I wouldn't call that a monolith then.
Well if you're distributing requests over multiple servers, I wouldn't call that a monolith.
Wait, so in what sense is it a monolith then? :D
Can you do concurrent reads to a disk? I actually don't know the answer to this. I'm pretty sure you can't on an HDD, but I don't know about an SSD.
> they went over how they handle a billion requests a day with mostly a Rails monolith 1 day has 246060=86400 seconds. 1bn/86400 is more than 10000 reqs/second, so each request has to be served in less than 100 us.…
That sounds specific to where you live. In London the buses are amazing.
Unrelated to git, but I LOVE how fast and user-friendly this page is.
This is yet another instance of a phenomenon: When you have good outcomes and bad outcomes, and you take some preventative measures to reduce the likelihood of bad outcomes, as time goes by people start believing that…