4 ms·
Complex systems decay over long periods of time.
by aappleby 4y ago
Complex systems decay over long periods of time.
- mirekrusin 4y agoI don't think system you can easily replicate while intoxicated during hackaton is inherently technically complex.
- qup 4y agoCounterpoint: you can't easily replicate twitter while intoxicated during a hackathon.
- jononor 4y agoTwitter has over 200 million Daily Active Users across the globe, with an average of 6000 tweets per second. Peak tweets per second is said to be over 100k. Each user gets a personalized feed which is regularly updated (I could not find numbers for views and update rate). All tweets going back to 2006 are accessible via URL, there are a few trillion of these. How would you solve this in a couple of days?
- qup 4y agoFirst, I'd buy a nice half-gallon of Maker's Mark.
- mirekrusin 4y agoI did have pleasure of working on a system where we had 60k concurrent writes (cloud storage, bulky writes, a lot of data) - it's really not a rocket science if it's not complicated and short messages + views on them is not that complicated. Computers are really fast today, you just don't do stupid things. Scalability problem has been already solved at twitter and there is nothing inherently complex with serving short public messages. Most things don't need to have short latency and they don't need to be 100% precise. As an example currently whole stack overflow runs on 9 on-premise servers.
- qup 4y agoYes, but that's if you engineer it that way. You're just saying it doesn't have to be a complex system. But Twitter is. I agree it doesn't have to be, but it has been for like 15 years or whatever.
- jononor 4y agoMy point was that it is not a two-day hack job, as claimed above. It is in no way a unique challenge, but neither is it trivial. Probably take multiple man-months for a small team that has built similar systems before.