InfoQ Homepage Scalability Content on InfoQ
-
Wave: a Case Study for Low Architectural Complexity
Dan Luu published an article presenting Wave as a case study for a business model where a simple and boring architecture fits best. Instead of a state-of-the-art service-based asynchronous architecture, they employ a synchronous monolith backed by a database and serving a unified API.
-
Integrating Continuous Load Testing into Slack Pipeline
Slack has been working on making load testing a core concern for all engineers, not only those focusing on performance, and moving from a reactive approach to performance to a more integrated effort, say Slack engineers Shreya Ramesh and Melissa Khuat.
-
Netflix’s RENO Keeps Experience Consistent across Devices
Netflix has developed the Rapid Event Notification System (RENO) to create a consistent user experience across various platforms and devices. RENO reacts more quickly and consistently than the traditional request/response model to user-generated actions ranging from watching a title to changing profile information.
-
Zesty Disk Provides Automatic Scaling for AWS EBS
Zesty recently released Zesty Disk, an automated scaling solution for AWS EBS. Zesty Disk monitors EBS performance metrics and can automatically scale the cluster size based on those metrics. This is done by creating a cluster of EBS volumes that can be attached or detached as needed based on system usage.
-
Google Meet’s Scaling Challenges during COVID-19
Google wrote about their challenges in scaling Google Meet due to increased usage since the COVID-19 pandemic led to more people using it. The SRE team at Google used their existing incident management framework with modifications to tackle the challenge of increased traffic that started earlier this year.
-
Khan Academy's Scaling Story to 2.5x Traffic Using a Serverless Architecture and CDN
Khan Academy’s engineering team shared their story of scaling to 2.5x their usual traffic by leveraging a serverless architecture on Google App Engine and their static content delivery providers Fastly and Youtube.
-
An Incremental Architecture Approach to Building Systems
Of most of the applications we have globally, maybe 90% of them are perfectly served by a monolithic approach. To avoid overengineering, we should start with a simple architecture and evolve it as needs arise, Randy Shoup recently declared in a presentation where he described his experience with companies that started small and then grew into large global internet companies.
-
Plaid.com’s Monitoring System for 9600+ Integrations
Plaid.com has integrations with over 9600 financial institutions, and their monitoring challenges arise from the heterogeneous nature of these integrations and as well as their large number. They rebuilt their monitoring system on Kinesis, Prometheus, Alertmanager and Grafana to solve the challenges of scalability and low latency.
-
How SendGrid Scales Its Email Delivery Systems
SendGrid, a cloud based email service, has seen its backend architecture evolve from a small Postfix installation to a system hosted on their own data-centers as well as on the public cloud. Rewriting of services in Go, a gradual move to AWS, and a distributed Ceph-based queue allows the team to hand over 40 billion emails per month.
-
GitHub Engineering Adopts New Architecture for MySQL High Availability
Github.com uses MySQL as a backbone for many of its critical services like the API, authentication and the Github.com website itself. Github’s engineering team replaced its previous DNS and VIP based setup with one based on Orchestrator, Consul and the Github Load Balancer to get around split brain and DNS caching issues.
-
How Edgemesh Rolled out Its P2P Web Acceleration Service to Production
Edgemesh is a P2P web acceleration service based on the WebRTC protocol suite that offloads some of the the traffic normally handled by traditional CDNs to browser-based caches shared over a P2P network. They rolled out their release to production in the last few months and shared some of their experiences.
-
The Long History of Microservices
Microservices has a very long history, not as short as many believe. Neither was SOA invented in the 90s. We have been working with the core ideas behind services for five decades, Greg Young explained at the recent Microservices Conference in London, during his presentation on working with microservices.
-
Gil Tene: Understanding Hardware Transactional Memory
In his presentation "Understanding Hardware Transactional Memory" at QCon New York 2016, Gil Tene introduces hardware transactional memory (HTM). Whereas the concept of HTM is not new, it is now finally available in commodity hardware. The purpose of HTM is to be able to write to multiple addresses in memory in an atomical way so that there cannot be inconsistencies in cooperation other threads.
-
LFE Brings Lisp to the Erlang Virtual Machine
After 8 years of development, Lisp Flavoured Erlang (LFE) has reached version 1.0, bringing stable support for Lisp programming on the Erlang virtual machine (BEAM). LFE was created by Robert Virding, one of the initial developers of Erlang. InfoQ has spoken with Duncan McGreggor, current maintainer of LFE.
-
Microsoft Makes Available Their Platform for Building Microservices
Microsoft has announced and made available the preview of Azure Service Fabric (ASF), a cloud platform including a runtime and lifecycle management tools for creating, deploying, running and managing microservices. ASF microservices can be deployed on Azure or on-premises on Windows Server private or hosted clouds. Support for Linux is to come in the future.