You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So 25QPS crashed the site? What is it running on, a Raspberry Pi?
This isn't rocket science. We handle ~1000 seat reservations per second for @euskalencounter on two servers with Python/Flask/PostgreSQL. How do people make things perform so poorly?
https://www.theguardian.com/politics/2019/mar/21/petitions-site-crashes-after-thousands-back-call-to-revoke-article-50?CMP=fb_gu …pic.twitter.com/Px5e8yiY90
Think about it, we can *encode 4K video* in real time on a modern server easily. That's 30 or 60 multi-megapixel images per second going through complex algorithms. Recording that someone clicked a button is trivial in comparison. How do people get this so wrong?
And for a petition site you can just dump records in a DB, and cache queries and counts. For reservations we actually need a hard cutoff when seats are exhausted and that introduces a bottleneck hotspot. A petition site is embarrassingly parallelizable.
Even a Pi could handle that comfortably, really.
> What is it running on, a Raspberry Pi? The UK goverment needs to promote the 𝕟𝕒𝕥𝕚𝕠𝕟𝕒𝕝 product.
As bad as that is, it doesn't sound unsurprising for the civil service, or a contractee.
Poor database schema design, probably.
True, caching / architecture is way more important than choice of technology
The answer to your question is and has always been Java Enterprise frameworks.
i still remember how we used Java EE around the end of college and tbh....it was terrible :(
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
