sdrwefgfvb

3 ms·

1. 1.▲
   by sdrwefgfvb 4y ago

   I wouldn't call that a monolith then.
2. 2.▲
   by sdrwefgfvb 4y ago

   Well if you're distributing requests over multiple servers, I wouldn't call that a monolith.
3. 3.▲
   by sdrwefgfvb 4y ago

   Wait, so in what sense is it a monolith then? :D
4. 4.▲
   by sdrwefgfvb 4y ago

   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.
5. 5.▲
   by sdrwefgfvb 4y ago

   > they went over how they handle a billion requests a day with mostly a Rails monolith 1 day has 24 60 60=86400 seconds. 1bn/86400 is more than 10000 reqs/second, so each request has to be served in less than 100 us. According
6. 6.▲
   by sdrwefgfvb 4y ago

   That sounds specific to where you live. In London the buses are amazing.
7. 7.▲
   by sdrwefgfvb 4y ago

   Unrelated to git, but I LOVE how fast and user-friendly this page is.
8. 8.▲
   by sdrwefgfvb 4y ago

   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 the bad outcomes don&#