Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we’re going to talk about how some systems have to dramatically scale to serve millions of users with an acceptable quality of service.
1. The Slack team has migrated the most critical user-facing services from a monolithic to a cell-based architecture over the last 1.5 years. But what is a “cell-based architecture”, and how does it work?
2. The Red Hat team has run tests to find out the maximum number of pods per node that can be run on OpenShift 4.13 clusters with equal or better performance, and the answer is 2500.
3. AWS S3 is the original object storage service with an HTTP REST API. It consists of a frontend with a REST API, a namespace service, a storage system full of hard disks, and many background operations. Andy Warfield, VP and distinguished engineer at S3, explains how AWS designed S3 for massive scalability.
4. Mainframe computers are often seen as ancient machines—practically dinosaurs. But mainframes, which are purpose-built to process enormous amounts of data, are still extremely relevant today. But how do they work, and who uses them? ArsTechnica reports.
5. Red Planet Labs just built a Twitter-scale Mastodon instance from scratch in only 10k lines of code, which they will soon open source, and it offers unprecedented scalability. Check it out.
Are your systems designed for scalability? Have you ever programmed mainframe applications? Would you like to share some scalability tips and tricks with our readers? Get in touch with us, and see you next week for another edition of VSHN.timer.
PS2: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.
PS3: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.