# High Scalability Building bigger, faster, more reliable websites. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Swedbank Outage shows that Change Controls don't work DevFeed: [The Swedbank Outage shows that Change Controls don't work]() Original publisher: [Read original article]() Author: Bruce Johnston Published: 2023-08-16T17:05:12Z Content type: opinion Language: en Sources: [High Scalability](), [High Scalability]() Topics: [incident](), [systems]() Tags: [banking](), [change](), [incident](), [management](), [outage](), [payments](), [risk-management]() ### AI overview The article examines the Swedbank outage caused by an unapproved IT change and the Swedish FSA's findings that the bank's internal controls and change management process failed. It argues that manual approvals and change meetings do not by themselves mitigate risk in modern technology organizations. ### Source excerpt This week I've been reading through the recent judgment from the Swedish FSA on the Swedbank outage. If you're unfamiliar with this story, Swedbank had a major outage in April 2022 that was caused by an unapproved change to their IT systems. It temporarily left nearly a million customers with incorrect balances, many of whom were unable to meet payments. After investigation, the regulator found that Swedbank had not followed their change management process and issued a SEK850M (~85M USD) fine. That's a lot of money to you and me, but probably didn't impact their bottom line very much. Either way I'm sure the whole episode will have been a big wake up call for the people at the bank whose job it is to ensure adequate risk and change controls. So, what went wrong and how could it have been avoided? How did the Swedbank incident happen? The judgment doesn't describe the technical details behind the incident, but it does provide glimpses into how they assessed what went wrong: "The deficiencies that were present in Swedbank's internal control made it possible to make changes to one of the bank's most central IT systems without following the process in place at the bank to ensure continuity and reliable operations. This violation is therefore neither minor nor excusable." "none of the bank's control mechanisms were able to capture the deviation and ensure that the process was followed" "one of the main causes underlying the IT incident was non-compliance with the change management process and that it is probable that this also resulted in a slower analysis of the incident and a greater impact on the operations." "good internal control is a prerequisite for a bank to be able to fulfill the requirements on risk management" Even if you think $85M isn't much of a fine - simply the cost of doing business - the full range of options open to the regulator included removing Swedbank's banking license: "It is therefore not relevant to withdraw Swedbank's authorisation or issue th ## Lessons Learned Running Presto at Meta Scale DevFeed: [Lessons Learned Running Presto at Meta Scale]() Original publisher: [Read original article]() Author: Philip Bell Published: 2023-07-16T16:42:21Z Content type: tutorial Language: en Sources: [High Scalability](), [High Scalability]() Topics: [SQL](), [Deployment](), [gateway](), [Open Source](), [Availability](), [releases](), [data centers](), [Hardware]() Tags: [analytics](), [automation](), [availability](), [data-centers](), [database-scalability](), [ddatabase](), [deployment](), [gateway](), [hardware](), [high-availablilty](), [high-performance](), [high-scalability](), [load-balancer](), [open-source](), [presto](), [releases](), [scalability](), [sql]() ### AI overview This article presents lessons from running Presto, an open source SQL query engine, at Meta scale. It discusses deploying new releases across many clusters, maintaining availability during updates, routing queries through the Gateway, and automating cluster operations. ### Source excerpt Presto is a free, open source SQL query engine. We've been using it at Meta for the past ten years, and learned a lot while doing so. Running anything at scale - tools, processes, services - takes problem solving to overcome unexpected challenges. Here are four things we learned while scaling up Presto to Meta scale, and some advice if you're interested in running your own queries at scale. Scaling Presto rapidly to meet growing demands: What challenges did we face? Deploying new Presto releases ## Gossip Protocol Explained DevFeed: [Gossip Protocol Explained]() Original publisher: [Read original article]() Author: NK Published: 2023-07-16T16:38:02Z Content type: article Language: en Sources: [High Scalability](), [High Scalability]() Topics: [Protocol (disambiguation)](), [distributed-systems](), [P2P](), [Availability](), [consistency](), [Scalability](), [Resilience](), [Network]() Tags: [availability](), [consistency](), [distributed](), [distributed-algorithm](), [distributed-system](), [distributed-systems](), [high-scalability](), [messages](), [network](), [protocol](), [resilience]() ### AI overview This article explains the gossip protocol as a peer-to-peer approach for managing state and communicating between nodes in distributed systems. It describes its relationship to high availability, eventual consistency, scalability, and resilience, and compares it with centralized state management, point-to-point broadcast, and eager reliable broadcast. ### Source excerpt You can subscribe to the system design newsletter to excel in system design interviews and software architecture. The original article was published on systemdesign.one website. What Is Gossip Protocol? The typical problems in a distributed system are the following [1], [11]: maintaining the system state (liveness of nodes) communication between nodes The potential solutions to these problems are as follows [1]: centralized state management service peer-to-peer state management service ## Consistent hashing algorithm DevFeed: [Consistent hashing algorithm]() Original publisher: [Read original article]() Author: NK Published: 2023-02-22T16:39:15Z Content type: tutorial Language: en Sources: [High Scalability](), [High Scalability]() Topics: [hashing](), [Algorithm](), [Cache](), [Scalability](), [distributed-systems](), [Software](), [Availability]() Tags: [algorithm](), [availability](), [cache](), [consistent-hashing](), [distributed-system](), [hashing](), [hotspot](), [load-balancing](), [low-latency](), [scalability](), [sharding](), [software-architecture]() ### AI overview A tutorial explaining consistent hashing: nodes and data keys are mapped onto a virtual hash ring, and clockwise traversal assigns data to nodes. It discusses terminology, cache-server scaling requirements, hotspot reduction, dynamic load, replication, availability, and latency. ### Source excerpt This is a guest article by NK. You can view the original article Consistent hashing explained on systemdesign.one website. How does consistent hashing work? At a high level, consistent hashing performs the following operations: The output of the hash function is placed on a virtual ring structure (known as the hash ring) The hashed IP addresses of the nodes are used to assign a position for the nodes on the hash ring The key of a data object is hashed using the same hash function to find the position of the key on the hash ring The hash ring is traversed in the clockwise direction starting from the position of the key until a node is found The data object is stored or retrieved from the node that was found Terminology ## What is Cloud Computing? According to ChatGPT. DevFeed: [What is Cloud Computing? According to ChatGPT.]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-12-16T17:04:08Z Content type: opinion Language: en Sources: [High Scalability](), [High Scalability]() Topics: [ChatGPT](), [cloud-computing](), [Artificial Intelligence](), [data-processing](), [Scalability]() Tags: [ai](), [chatgpt](), [cloud-computing](), [efficiency](), [networking](), [servers]() ### AI overview An opinion article presents ChatGPT's explanation of cloud computing and evaluates it as broad and polished but lacking depth. It argues that AI and machine-learning tools are more likely to augment people than replace them, while the supplied excerpt describes cloud computing's on-demand access to shared resources and benefits such as scalability, flexibility, and efficiency. ### Source excerpt DALL-E picture generated from the answer. I was curious, given all the ChatGPT love, what it would make of some of our favorite topics. I was both impressed and unimpressed. Impressed. ChatGPT instantly generated an response that might make a good answer in a Miss Universe contest. You know, the kind of answer delivered with a radiant smile calculated to offend no one yet still sounds comprehensive and deep. Unimpressed. The answers are a mile wide and an inch deep. There's not a lot of insight. It's more of a zeitgeist oracle. Nothing wrong with that, but I don't think we'll be unemployed soon. It's as many have predicted about AI/ML. These are tools to augment us, flawed humans, not replace us...yet. Thank you for agreeing to be interviewed today. You're welcome! I'm happy to answer any questions you have. Please go ahead and ask your first question. Explain cloud computing to me at a professional level? Cloud computing is a model of computing that delivers computing services over the internet, including storage, data processing, and networking. It allows users to access and use shared computing resources, such as servers, storage, and applications, on demand and without the need to manage the underlying infrastructure. This model of computing has become increasingly popular in recent years, as it offers a number of benefits, including cost savings, flexibility, scalability, and increased efficiency. Additionally, cloud computing allows for greater collaboration and innovation, as it enables users to access and share data and resources from anywhere, at any time. Can you expand? Certainly. Cloud computing has become a widely-used model of computing, as it offers a number of benefits over traditional, on-premises computing systems. One of the key benefits of cloud computing is its scalability, which allows users to easily and quickly scale up or down their use of computing resources, depending on their changing needs. This means that users only pay for the computin ## Stuff The Internet Says On Scalability For December 2nd, 2022 DevFeed: [Stuff The Internet Says On Scalability For December 2nd, 2022]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-12-02T17:08:30Z Content type: article Language: en Sources: [High Scalability](), [High Scalability]() Topics: [Scalability]() Tags: [hot-links](), [scalability]() ### AI overview A roundup of scalability-related statistics, announcements, and quotations, including figures about APIs, caching, cloud services, network traffic, and security incidents. ### Source excerpt Never fear, HighScalability is here! 1958: An engineer wiring an early IBM computer 2021: An engineer wiring an early IBM quantum computer. @enclanglement My Stuff: I'm proud to announce a completely updated and expanded version of Explain the Cloud Like I'm 10! This version adds 2x more coverage, with special coverage of AWS, Azure, GCP, and K8s. It has 482 mostly 5 star reviews on Amazon. Here's a 100% organic, globally sourced review: Love this Stuff? I need your support on Patreon to keep this stuff going. Number Stuff: ## The Cloud is Not a Railroad - An Argument Against the Vertical Separation of Cloud Providers DevFeed: [The Cloud is Not a Railroad - An Argument Against the Vertical Separation of Cloud Providers]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-10-24T11:52:23Z Content type: opinion Language: en Sources: [High Scalability](), [High Scalability]() Topics: [Cloud](), [cloud-infrastructure]() Tags: [argument](), [cloud](), [infrastructure](), [platform](), [providers](), [services]() ### AI overview An argument against vertically separating cloud providers. The article contends that structural separation would not solve the underlying problems and could limit the quality of software developers build by restricting the services cloud providers can offer. ### Source excerpt There's a move to regulate cloud providers by vertically separating the services they offer. Like railroads of yore, who were not allowed to provide freight services on top of their base services, cloud providers would not be allowed to provide services on top of their base platform services. Vertical separation would be new to the cloud industry. Is it a good idea? Would it actually solve any problems? My answers are no and no, but probably not for the reasons you think. Let's dive in. Here are a few useful resources for exploring this argument: Maintaining monopolies with the cloud by Cory Doctorow. https://pluralistic.net/2022/09/28/other-peoples-computers. A group advocating for fair licensing. https://www.fairsoftwarelicensing.com/our-principles. Cloud Infrastructure Services -- An analysis of potentially anti-competitive practices by Professor Frédéric Jenny. https://www.fairsoftwarestudy.com/. Now Cory is about 100x times smarter than I am, but this analogy is wrong: That's why the trustbusters were so big on "structural separation": the principle that a business can own a platform or use the platform, but not both. So this remedy is also wrong: Rather than trying to construct rules that kept the referee honest even when they played on one of the teams, they ordered the companies to choose one role - either you were the ref, or you were a player, but you couldn't referee a match where you were also in the competition. Because this idea, while trivially true, misses the point: There is no cloud, there is only other people's computers. This is like saying there is no human body, it's just a collection of cells. While true, it is the lesser truth that fails to recognize the importance of the body, organs, and the adaptive function of the brain. That's what a cloud provider is; it's the body electric for the cloud. The report by Professor Jenny seems to be the main support for cleaving cloud providers in two. I've read the report. Is there a smoking gun? Not that ## Sponsored Post: G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte DevFeed: [Sponsored Post: G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-07-18T14:38:51Z Content type: opinion Language: en Sources: [High Scalability](), [High Scalability]() Topics: [DevOps](), [Back end](), [Databases](), [Monitoring](), [hosting](), [JavaScript](), [Linux](), [Ansible](), [PHP](), [WordPress]() Tags: [ansible](), [backend](), [databases](), [developer](), [developers](), [devops](), [hosting](), [javascript](), [linux](), [monitoring](), [sponsored](), [sponsored-post](), [wordpress]() ### AI overview A sponsored post compiling hiring and promotional opportunities from companies including Close, Wynter, Kinsta, InterviewCamp.io, and Triplebyte. The listings cover site reliability, system administration, DevOps, JavaScript development, research participation, and interview preparation. ### Source excerpt Who's Hiring? Close is building the sales communication platform of the future and we're looking for a Site Reliability Engineer to help us accomplish that goal. If you have a passion for databases (both SQL and NoSQL), significant experience building, managing, and monitoring infrastructure, databases, and backend services at scale and want to work with a rag-tag team of hardworking, but humble humans, then come check us out! Wynter is looking for system administrators, engineers, and developers to join its research panel. Participate in research surveys, get paid ($90-$180/hr) for your feedback and comments. Super low key commitment, 10-15 mins per survey. Learn more and sign up. DevOps Engineer: At Kinsta, we set out to create the best managed hosting platform in the world. If you are an experienced DevOps Engineer who is constantly looking for ways to innovate and improve, we might just be the place for you! As Kinsta's DevOps Engineer, you will be instrumental in making sure that our infrastructure is always on the bleeding edge of technology, remaining stable and high-performing at all times. If you love working with Linux, have a background in PHP, and have worked with cutting-edge technologies, such as Ansible and LXC, check us out and apply here. SysOps Engineer: As Kinsta's SysOps Engineer, you'll play a key role in caring for the health of our servers, preventing issues, and responding immediately to mitigate any problems in our infrastructure. If you have experience in hosting and with the WordPress stack, have worked with Ubuntu or Debian-based systems, and cutting-edge technologies, such Ansible and LXC, you should definitely check us out and apply here! JavaScript Developer: Kinsta's Development Team aims to create truly effective solutions for our customers and our internal teams. We believe the only way to maintain and scale our standards is to focus on quality code. If you are a talented JavaScript developer and you would like to work with an owner ## Stuff The Internet Says On Scalability For July 11th, 2022 DevFeed: [Stuff The Internet Says On Scalability For July 11th, 2022]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-07-11T16:11:55Z Content type: article Language: en Sources: [High Scalability](), [High Scalability]() Topics: [Scalability](), [Internet](), [Architecture & Design]() Tags: [attacks](), [cloud](), [cloudflare](), [concurrent](), [data](), [gdpr](), [go](), [hot-links](), [kafka](), [kubernetes](), [latency](), [on-prem](), [performance](), [scalability](), [servers](), [stack-overflow]() ### AI overview A July 11, 2022 HighScalability roundup collects assorted internet items about scalability, including infrastructure figures, Kubernetes and Cloudflare examples, Stack Overflow and Riot Games workloads, Go generics performance, processor design, concurrent connections, Wi-Fi security, and GDPR fines. ### Source excerpt Never fear, HighScalability is here! Every cell a universe. Most detailed image of a human cell to date. @microscopicture Other images considered: one byte of RAM in 1946; visual guide on troubleshooting Kubernetes; Cloudflare using lava lamps to generate cryptographic keys; 5MB of data looked like in 1966 My Stuff: Love this Stuff? I need your support on Patreon to help keep this stuff going. Know anyone who needs to go from zero to cloud? My book teaches them all they need to know about the cloud. Explain the Cloud Like I'm 10. It has 440 mostly 5 star reviews on Amazon. Here's a 100% sincere, heartfelt review: Do you like Zone 2, Zone 5, interval, REHIT, HIIT, and bodyweight workouts? I made an app for that. Max Workout. I'm not just the programmer, I'm a client. I use it 4 times a week and if you want to retrain your mitochondria, get fit, get healthy, and live longer, I think you'll like it too. Number Stuff: ## Sponsored Post: G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte DevFeed: [Sponsored Post: G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-06-10T15:39:03Z Content type: article Language: en Sources: [High Scalability](), [High Scalability]() Topics: [DevOps](), [site-reliability-engineer](), [Databases](), [Monitoring](), [Ansible](), [hosting](), [Linux](), [PHP](), [JavaScript](), [NoSQL](), [WordPress](), [Ubuntu]() Tags: [ansible](), [databases](), [debian](), [devops](), [hosting](), [javascript](), [linux](), [lxc](), [monitoring](), [nosql](), [php](), [site-reliability-engineer](), [sponsored](), [sponsored-post](), [ubuntu](), [wordpress]() ### AI overview A sponsored post presents hiring and promotional opportunities from several technology companies, including Site Reliability Engineer, DevOps Engineer, SysOps Engineer, and JavaScript Developer roles. It highlights experience with databases, infrastructure, backend services, Linux, PHP, Ansible, LXC, hosting, WordPress, and JavaScript. ### Source excerpt Who's Hiring? Close is building the sales communication platform of the future and we're looking for a Site Reliability Engineer to help us accomplish that goal. If you have a passion for databases (both SQL and NoSQL), significant experience building, managing, and monitoring infrastructure, databases, and backend services at scale and want to work with a rag-tag team of hardworking, but humble humans, then come check us out! Wynter is looking for system administrators, engineers, and developers to join its research panel. Participate in research surveys, get paid ($90-$180/hr) for your feedback and comments. Super low key commitment, 10-15 mins per survey. Learn more and sign up. DevOps Engineer: At Kinsta, we set out to create the best managed hosting platform in the world. If you are an experienced DevOps Engineer who is constantly looking for ways to innovate and improve, we might just be the place for you! As Kinsta's DevOps Engineer, you will be instrumental in making sure that our infrastructure is always on the bleeding edge of technology, remaining stable and high-performing at all times. If you love working with Linux, have a background in PHP, and have worked with cutting-edge technologies, such as Ansible and LXC, check us out and apply here. SysOps Engineer: As Kinsta's SysOps Engineer, you'll play a key role in caring for the health of our servers, preventing issues, and responding immediately to mitigate any problems in our infrastructure. If you have experience in hosting and with the WordPress stack, have worked with Ubuntu or Debian-based systems, and cutting-edge technologies, such Ansible and LXC, you should definitely check us out and apply here! JavaScript Developer: Kinsta's Development Team aims to create truly effective solutions for our customers and our internal teams. We believe the only way to maintain and scale our standards is to focus on quality code. If you are a talented JavaScript developer and you would like to work with an owner