Rendering even the simplest web page on Twitter requires the collaboration of dozens of network services speaking many different protocols.

Let's take a look how Twitter Dev team is pulling this off building robust systems!

A thread 🧵 In such large scale production systems, a frequent cause of outages is poor interaction between components in the presence of failures; common failures include crashed hosts and extreme latency variance.

Cloud native, Highly scalable, Document graph db? Surreal? It is!

A thread 🧵

#cloudnative #graphdb @SurrealDB is an end-to-end cloud native database for web, mobile, serverless, jamstack, backend, and traditional applications.

While cache accounts for ~3% of @Twitter's architecture, but it's really critical for them. Here's how they've been managing it. 🤯🤯

A thread 🧵

#engineeringXplored Despite the availability of Twemcache and Redis, both highly popular and seemingly mature projects, existing solutions don’t really fully answer the cache requirements and challenges Twitter faces🤯🤯

In the age of the unicorn startups, @SlackHQ has drawn attention for its rise and potential for disrupting traditional business communications tools, particularly email. You also must've used it sometime recently!

#engineeringXplored

A thread 🧵 Slack's IT architecture is based on a broad range of services offered by AWS. EC2 for compute tasks, Blockstore for nightly backups, S3 for file uploads and asset management, VPC for security groups and firewall rules to name some.