Discover and read the best of Twitter Threads about #engineeringXplored
Most recents (2)
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
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🤯🤯
Pelikan addresses most of these caching issues by treating cache servers as a framework, abstracting common functionalities as modules, and implementing features against common interfaces.
Written in Rust and C👨💻
Written in Rust and C👨💻
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 🧵
#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.
Along with the AWS services, Slack is using the Redis data structure server, the Apache Solr search tool, the Squid caching proxy, and a MySQL database.
The web client is built with JS and ES6 with ReactJS, Desktop app with Electron.
The web client is built with JS and ES6 with ReactJS, Desktop app with Electron.
