I find it funny that backend devs will do all this infrastructure work to support billions of real time messages and then frontend devs stomp all over it by making the app take 500MB of RAM and hundreds of ms to take basic actions.
Given how intelligent people are, I would not be surprised if this is by choice. They probably don't want poor pleba using their software anyway, just those with money to spare
Honest question, does anyone appreciate these “case studies”? It seems like they’re always based on some random quote and they go way in detail on what the various technologies are and how they might possibly apply to the subject in question, but with almost no real insight besides “I think this is how it might work”. What kind of case study is that?! If you don’t have real examples how is this better than just presenting the original source for the quote and Wikipedia links to the various technical terms?
Whenever I read about these web startup architectures I notice there is never a baseline comparison. They start with an insane architecture and then do heroics to transform it into something a little better.
If you have a fast cgi service inserting a text message into a Postgres database, how many messages do you need until that doesn’t work?
Discord, especially the mobile app, is some of the shittiest, broken software I have encountered. The core protection team is absolute trash at their job
10 comments
[ 7.1 ms ] story [ 46.9 ms ] threadIf you have a fast cgi service inserting a text message into a Postgres database, how many messages do you need until that doesn’t work?
Discord, especially the mobile app, is some of the shittiest, broken software I have encountered. The core protection team is absolute trash at their job