Skip to content
Tagged articles

fault tolerance

355 articles · Page 4 of 4
ITFLY8 Architecture Home
ITFLY8 Architecture Home
May 19, 2018 · Backend Development

How to Structure Functional Teams and Service Patterns for Scalable Microservices

This article explains how Conway's law guides functional team division in microservice architectures, describes decentralized governance, outlines various interaction and composition patterns, discusses fault‑tolerance mechanisms such as isolation, circuit breaking, rate limiting, and provides guidance on choosing appropriate service granularity.

architecturefault tolerancemicroservices
0 likes · 32 min read
How to Structure Functional Teams and Service Patterns for Scalable Microservices
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Mar 24, 2018 · Operations

How Service Degradation and Fault‑Tolerance Keep Large‑Scale Systems Resilient

This article explains how setting low timeouts for non‑core services, decoupling and physically isolating micro‑services, separating light and heavy workloads, and implementing automated configuration checks together enhance system reliability and reduce both technical and human errors in high‑traffic environments.

Configuration Managementfault tolerancesystem reliability
0 likes · 9 min read
How Service Degradation and Fault‑Tolerance Keep Large‑Scale Systems Resilient
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Mar 22, 2018 · Operations

How Simple Retry Can Crash Your System and Smarter Alternatives

This article examines the pitfalls of naive retry mechanisms, explores active‑standby service switching, dynamic removal of unhealthy nodes, proper timeout configuration, and anti‑reentrancy strategies to improve system reliability and prevent cascading failures in large‑scale backend operations.

RetryTimeoutfault tolerance
0 likes · 14 min read
How Simple Retry Can Crash Your System and Smarter Alternatives
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Mar 4, 2018 · Operations

Mastering Service Fault Tolerance: Key Patterns for Resilient Microservices

Effective fault tolerance is crucial for microservice stability, and this article explores core design principles and classic patterns—such as timeout retries, rate limiting, bulkhead isolation, circuit breakers, and fallback strategies—guiding developers to choose and combine the right approaches for high‑availability systems.

Circuit Breakerbulkheadfault tolerance
0 likes · 8 min read
Mastering Service Fault Tolerance: Key Patterns for Resilient Microservices
Efficient Ops
Efficient Ops
Feb 23, 2018 · Operations

What a Decade of Ops Taught Me: Key Strategies for Scalable Infrastructure

This article reflects on ten years of Tencent's operations experience, sharing the author's career journey, the evolution of large‑scale service management, the design of the L5 fault‑tolerant system, unified frameworks, resource packaging, CMDB virtual mirrors, and automated deployment practices that together enable reliable, efficient, and scalable infrastructure.

CMDBOperationsautomation
0 likes · 11 min read
What a Decade of Ops Taught Me: Key Strategies for Scalable Infrastructure
Tencent TDS Service
Tencent TDS Service
Feb 1, 2018 · Backend Development

How a TV App’s Waterfall Layout Boosted User Engagement and Efficiency

This article details the redesign of a TV app from a horizontal layout to a waterfall flow, explaining the project timeline, advantages, new seven‑layer architecture, CMS‑driven configuration, compatibility handling, pagination strategies, caching, and fault‑tolerance measures that together improved user conversion and system robustness.

CMSPaginationTV app
0 likes · 36 min read
How a TV App’s Waterfall Layout Boosted User Engagement and Efficiency
21CTO
21CTO
Nov 20, 2017 · Operations

Mastering High Availability and Concurrency: Core Principles and Practical Techniques

This article distills essential guiding principles, high‑availability strategies, and high‑concurrency techniques for building resilient, scalable systems, covering stateless design, fault‑handling phases, replication, isolation, rate limiting, caching, async processing, multithreading, and scaling approaches.

High Availabilityfault tolerancehigh concurrency
0 likes · 21 min read
Mastering High Availability and Concurrency: Core Principles and Practical Techniques
Efficient Ops
Efficient Ops
Nov 15, 2017 · Big Data

How Tencent Built a 10 TB‑Per‑Day Full‑Link Log Monitoring Platform

This article explains how Tencent's ZhiYun full‑link log monitoring platform handles massive daily logs, overcomes challenges of diverse log formats, high throughput, fault‑tolerant design, and provides scalable storage, query, and alerting capabilities for distributed micro‑service environments.

big datadata pipelinedistributed systems
0 likes · 10 min read
How Tencent Built a 10 TB‑Per‑Day Full‑Link Log Monitoring Platform
21CTO
21CTO
Oct 22, 2017 · Operations

How to Build Highly Available Systems: Fault Tolerance and Scalability Strategies

This article explains why high availability is critical for internet services, outlines key techniques such as stateless design, service discovery, heartbeat checks, idempotent operations, load balancing, throttling, caching, and micro‑service architecture, and discusses the operational challenges and monitoring tools needed to maintain resilient, scalable systems.

High AvailabilityIdempotencyService Discovery
0 likes · 8 min read
How to Build Highly Available Systems: Fault Tolerance and Scalability Strategies
Architecture Digest
Architecture Digest
Oct 15, 2017 · Operations

High Concurrency and High Availability Design Principles

This article outlines essential high‑concurrency and high‑availability principles—including stateless design, service decomposition, caching strategies, message queues, data heterogeneity, degradation, rate limiting, traffic switching, and rollback mechanisms—to help architects build scalable, reliable, and resilient systems.

High Availabilityarchitecturefault tolerance
0 likes · 12 min read
High Concurrency and High Availability Design Principles
21CTO
21CTO
Sep 26, 2017 · Operations

Why You Should Never Trust Any Component in Your System—and How to Protect It

In programming and operations, every element—from services and dependencies to requests, machines, data centers, power, networks, and humans—can fail unexpectedly, so you must assume distrust and implement defensive measures such as monitoring, redundancy, rate limiting, fallback strategies, backups, and automated deployment.

OperationsSecurityfault tolerance
0 likes · 9 min read
Why You Should Never Trust Any Component in Your System—and How to Protect It
21CTO
21CTO
Aug 11, 2017 · Operations

Alibaba’s Double 11 Playbook: Scaling Architecture and Real‑Time Fault Tolerance

Alibaba’s eight‑year evolution of Double 11 showcases how limited cost can deliver maximal user experience and massive throughput by transitioning from a centralized 3.0 distributed architecture to multi‑active zones, employing capacity planning, full‑link stress testing, fine‑grained dependency governance, and dynamic traffic scheduling to ensure high availability.

capacity planningfault tolerancelarge-scale e-commerce
0 likes · 12 min read
Alibaba’s Double 11 Playbook: Scaling Architecture and Real‑Time Fault Tolerance
Architecture Digest
Architecture Digest
Jul 16, 2017 · Operations

Fault Governance in Distributed Systems: Dependency Failures, Strong/Weak Dependency, and Fault‑Injection Practices

This article presents a comprehensive overview of fault governance in large‑scale distributed systems, covering classic dependency failures, the concept of strong and weak dependencies, experimental observations, the evolution of fault‑injection techniques, and best practices for building reliable fault‑drill platforms.

Dependency ManagementOperationschaos engineering
0 likes · 20 min read
Fault Governance in Distributed Systems: Dependency Failures, Strong/Weak Dependency, and Fault‑Injection Practices
Architecture Digest
Architecture Digest
Jul 6, 2017 · Fundamentals

PacificA: Microsoft’s General Replication Framework for Large‑Scale Distributed Storage Systems

PacificA is Microsoft’s generic replication framework for large‑scale distributed storage systems that provides strong consistency, separates configuration management from data replication, and uses a primary‑secondary model with lease‑based fault detection to ensure availability, correctness, and efficient operation across heterogeneous nodes.

ConsistencyPacificAReplication
0 likes · 14 min read
PacificA: Microsoft’s General Replication Framework for Large‑Scale Distributed Storage Systems
Suning Technology
Suning Technology
May 18, 2017 · Big Data

Why Apache Flink Beats Spark and Storm in Stream Processing

This article examines Apache Flink's stream‑processing architecture, compares its native streaming model, fault‑tolerance, performance and SQL capabilities with Spark and Storm, and concludes that Flink offers a more powerful and efficient solution despite some maturity gaps.

Apache FlinkSparkStorm
0 likes · 12 min read
Why Apache Flink Beats Spark and Storm in Stream Processing
Alibaba Cloud Developer
Alibaba Cloud Developer
May 12, 2017 · Operations

How Alibaba Engineers Fault Governance and Chaos Engineering for E‑commerce

This article recounts Alibaba's middleware team's QCon Beijing 2017 presentation on fault governance and fault‑drill practices, covering distributed‑system dependency failures, strong/weak dependency concepts, multi‑stage technical evolution, and the design of their chaos‑engineering platform for large‑scale e‑commerce.

AlibabaOperationschaos engineering
0 likes · 21 min read
How Alibaba Engineers Fault Governance and Chaos Engineering for E‑commerce
DevOps
DevOps
May 8, 2017 · Backend Development

Key Technical Concerns and Core Components of Microservices Architecture

Microservices architecture introduces technical concerns such as service registration, discovery, load balancing, health checks, front-end routing, fault tolerance, dynamic configuration, and framework selection, with common solutions ranging from centralized and in-process load balancers to Netflix and Spring Cloud components.

FrameworksService Discoveryfault tolerance
0 likes · 16 min read
Key Technical Concerns and Core Components of Microservices Architecture
Alibaba Cloud Developer
Alibaba Cloud Developer
Apr 21, 2017 · Big Data

How Alibaba Tackles Real-Time Stream and Graph Computing at Scale

In his ASPLOS keynote, Alibaba’s Vice President Zhou Jingren detailed the company’s large‑scale stream and graph computing platforms, highlighting fault‑tolerance innovations, real‑time data challenges, and upcoming advances in graph analytics and massive machine‑learning workloads.

AIAlibababig data
0 likes · 7 min read
How Alibaba Tackles Real-Time Stream and Graph Computing at Scale
Architecture Digest
Architecture Digest
Apr 16, 2017 · Operations

Common Load‑Balancing Strategies and Their Reliability Analysis in Distributed Systems

The article reviews hardware and software load‑balancing, explains classic strategies such as round‑robin, random, minimum‑response‑time, least‑connections and hash, and quantitatively evaluates their fault‑tolerance using probability formulas and example scenarios in distributed systems.

Least Connectionsdistributed systemsfault tolerance
0 likes · 10 min read
Common Load‑Balancing Strategies and Their Reliability Analysis in Distributed Systems
Qunar Tech Salon
Qunar Tech Salon
Feb 23, 2017 · Backend Development

Microservice Fault Tolerance: Timeout, Retry, Circuit Breaker, Rate Limiting, and Service Degradation

This article explains microservice fault‑tolerance techniques—including timeout settings, retry strategies, circuit‑breaker logic, current limiting, resource isolation, and service degradation—from both micro and macro perspectives, illustrating how to design resilient service chains and avoid cascading failures.

Circuit BreakerRetryTimeout
0 likes · 11 min read
Microservice Fault Tolerance: Timeout, Retry, Circuit Breaker, Rate Limiting, and Service Degradation
Tencent Cloud Developer
Tencent Cloud Developer
Feb 14, 2017 · Databases

TDSQL Audit Capability: Architecture, Kafka Integration, and Consistency Hash Implementation

TDSQL’s cloud‑based audit solution combines a three‑proxy high‑availability layer, Kafka’s O(1) persistent messaging, and a distributed audit‑server that uses consistent hashing and multi‑coroutine processing to consume data within seconds, while fault‑tolerant offsets, majority acknowledgments, and Tencent Cloud MongoDB storage ensure secure, ordered, scalable, and highly reliable audit logging.

Consistent HashingKafkaMongoDB
0 likes · 7 min read
TDSQL Audit Capability: Architecture, Kafka Integration, and Consistency Hash Implementation
Tencent Cloud Developer
Tencent Cloud Developer
Feb 9, 2017 · Backend Development

Backend Design and Implementation of QQ Game Spring Festival Red Packet System

The article details the QQ Game Spring Festival Red Packet backend, describing its multi‑phase architecture that handles 80 k RPS, uses CDN‑served static gift data, two‑level sorting, CMEM caching, RocketMQ buffering for throttled delivery, idempotent order tracking for fault tolerance, and unified real‑time monitoring.

Asynchronous ProcessingBackendfault tolerance
0 likes · 16 min read
Backend Design and Implementation of QQ Game Spring Festival Red Packet System
Efficient Ops
Efficient Ops
Feb 6, 2017 · Operations

Building Billion‑Scale Web Systems That Auto‑Extinguish Failures

The article shares Tencent’s practical fault‑tolerance journey for a billion‑scale activity platform, covering retry strategies, automatic removal of faulty nodes, timeout tuning, business‑level safeguards, service degradation, and decoupling techniques that together reduce manual firefighting and improve system resilience.

Operationsfault tolerancelarge-scale systems
0 likes · 25 min read
Building Billion‑Scale Web Systems That Auto‑Extinguish Failures
dbaplus Community
dbaplus Community
Jan 15, 2017 · Databases

How JD’s JIMDB Achieves Zero‑Downtime Scaling and Automatic Failover for Massive Caches

JIMDB is JD’s in‑house distributed cache platform that combines automatic fault detection, seamless online scaling, multi‑language support, and containerized deployment to replace traditional Memcached/Redis solutions, offering features such as one‑click cluster creation, elastic expansion, lossless scaling, and comprehensive monitoring for high‑traffic e‑commerce services.

CacheElastic Scalingdistributed systems
0 likes · 23 min read
How JD’s JIMDB Achieves Zero‑Downtime Scaling and Automatic Failover for Massive Caches
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Nov 27, 2016 · Backend Development

Why Microservices? Benefits, Features, and Real-World Frameworks Explained

This article explains why microservices are chosen over monolithic architectures, outlines their key characteristics, reviews popular frameworks such as Netflix's stack and Spring Cloud, and discusses essential concerns like service discovery, load balancing, security, configuration, monitoring, and fault tolerance.

Service Discoveryfault tolerancemicroservices
0 likes · 10 min read
Why Microservices? Benefits, Features, and Real-World Frameworks Explained
High Availability Architecture
High Availability Architecture
Nov 25, 2016 · Backend Development

Disque: An Experimental Distributed In‑Memory Message Queue – Design and Usage Overview

Disque is an experimental, distributed, fault‑tolerant in‑memory message queue built in C that extends Redis concepts with synchronous replication, configurable delivery semantics, explicit acknowledgments, fast‑ack support, dead‑letter handling, and optional disk persistence for robust backend messaging workloads.

BackendDisqueIn-Memory
0 likes · 17 min read
Disque: An Experimental Distributed In‑Memory Message Queue – Design and Usage Overview
Meituan Technology Team
Meituan Technology Team
Nov 11, 2016 · Operations

Common Service Fault Tolerance Patterns

The article explains how Meituan‑Dianping applies classic fault‑tolerance patterns—timeout and retry, rate limiting/load shedding, circuit breaker, bulkhead isolation, and fallback—to design for failure, prevent cascading service outages, and enhance system stability and high‑availability in a service‑oriented architecture.

Circuit BreakerRetrybulkhead
0 likes · 14 min read
Common Service Fault Tolerance Patterns
MaGe Linux Operations
MaGe Linux Operations
Nov 7, 2016 · Big Data

How HDFS Achieves Low Cost, High Reliability, and Fault Tolerance

This article explains how HDFS, inspired by Google’s GFS, provides a low‑cost, highly reliable, fault‑tolerant, and high‑performance distributed file system for big‑data workloads by using replication, standby NameNodes, block storage, rack awareness, and compute‑close‑to‑data strategies.

HDFSbig datadata replication
0 likes · 7 min read
How HDFS Achieves Low Cost, High Reliability, and Fault Tolerance
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Oct 14, 2016 · Fundamentals

Understanding Paxos: How Distributed Systems Reach Consensus

This article provides a vivid explanation of the Paxos algorithm, illustrating how it achieves reliable consensus among unreliable processors through a two‑phase prepare/promise and propose/accept process, using distributed auction analogies, message sequencing, and read/write operations to ensure consistency in distributed systems.

AlgorithmDistributed ConsensusRead/Write
0 likes · 15 min read
Understanding Paxos: How Distributed Systems Reach Consensus
21CTO
21CTO
Jul 30, 2016 · Operations

Building a 3‑Minute Fault Detection, 5‑Minute Recovery HA System for Games

This article explains how Alibaba’s NineGame platform achieved ultra‑high availability by shifting from system‑centric to business‑centric design, defining measurable goals (3‑minute issue detection, 5‑minute recovery, bi‑monthly incidents) and implementing a layered, automated, visual monitoring, client‑side retry, HTTP‑DNS, functional isolation, and multi‑site active‑active architecture.

Operationsbusiness‑centric designfault tolerance
0 likes · 22 min read
Building a 3‑Minute Fault Detection, 5‑Minute Recovery HA System for Games

Designing a Business‑Oriented High Availability Architecture for a Game Access System

The article presents a business‑centric high‑availability solution for a large‑scale game access platform, detailing measurable goals, a three‑dimensional architecture that includes client‑side retry, HTTP‑DNS, functional separation, multi‑region active‑active deployment, and automated, visual monitoring to achieve rapid problem detection, recovery, and minimal outage frequency.

business continuitydistributed systemsfault tolerance
0 likes · 23 min read
Designing a Business‑Oriented High Availability Architecture for a Game Access System
Qunar Tech Salon
Qunar Tech Salon
Jul 7, 2016 · Backend Development

Design and Practices of Qunar's Self‑Developed High‑Availability Message Middleware

This article shares Qunar's architecture and practical experience in designing a self‑developed high‑availability message middleware, covering its role in transaction processing, consistency guarantees, fault‑tolerance mechanisms, isolation, monitoring, and consumer design, and discusses trade‑offs and operational considerations.

Consistencyfault tolerance
0 likes · 16 min read
Design and Practices of Qunar's Self‑Developed High‑Availability Message Middleware
WeChat Backend Team
WeChat Backend Team
Jun 22, 2016 · Fundamentals

How PhxPaxos Turns Paxos Theory into a Production‑Grade Consensus Library

This article provides a beginner-friendly, engineering-focused overview of the production‑grade Paxos library PhxPaxos, explaining the consensus protocol, its roles, instance management, state‑machine integration, performance optimizations, multi‑group deployment, and practical considerations such as disk durability, leader election, and log checkpointing.

Distributed ConsensusPaxosProduction-Grade
0 likes · 30 min read
How PhxPaxos Turns Paxos Theory into a Production‑Grade Consensus Library
Architecture Digest
Architecture Digest
Apr 8, 2016 · Operations

Practical Fault‑Tolerance Practices in a Large‑Scale Activity Operations Platform

This article shares the author’s experience building fault‑tolerance for Tencent’s activity operations platform, covering retry strategies, automatic removal of unhealthy machines, timeout tuning, asynchronous processing, anti‑replay mechanisms, service degradation, service decoupling, and business‑level safeguards to reduce manual alarm handling and improve system robustness.

OperationsRetryTimeout
0 likes · 21 min read
Practical Fault‑Tolerance Practices in a Large‑Scale Activity Operations Platform
21CTO
21CTO
Apr 5, 2016 · Operations

How Tencent’s AMS Achieved Fault Tolerance at Billion‑Request Scale

This article shares Tencent’s experience building fault‑tolerant mechanisms for the AMS activity platform, covering retry strategies, automatic machine exclusion, timeout tuning, service isolation, asynchronous processing, anti‑replay safeguards, and operational best practices that transformed a million‑request service into an 800‑million‑request system.

Asynchronous ProcessingOperationsRetry
0 likes · 24 min read
How Tencent’s AMS Achieved Fault Tolerance at Billion‑Request Scale
21CTO
21CTO
Mar 25, 2016 · Operations

How Different Load‑Balancing Strategies Impact Reliability in Distributed Systems

This article examines common load‑balancing algorithms—round‑robin, random, minimum response time, minimum concurrency, and hash—analyzing their fault‑tolerance in distributed clusters, deriving success‑rate formulas, and showing why strategies like minimum concurrency outperform simple methods under node failures.

distributed systemsfault toleranceload-balancing
0 likes · 12 min read
How Different Load‑Balancing Strategies Impact Reliability in Distributed Systems
ITPUB
ITPUB
Jan 15, 2016 · Backend Development

Understanding Microservices: Concepts, Benefits, and Practical Implementation

This article explains what microservices are, compares them with monolithic architecture, outlines their key characteristics, and provides practical guidance on client access, inter‑service communication, service discovery, fault tolerance, and deployment considerations.

API GatewayBackendService Discovery
0 likes · 13 min read
Understanding Microservices: Concepts, Benefits, and Practical Implementation
Qunar Tech Salon
Qunar Tech Salon
Dec 15, 2015 · Big Data

Real-Time Computing with Apache Storm: Architecture, Code Samples, and Fault Tolerance

This article explains the principles of real-time computing, compares it with offline batch processing, and demonstrates a practical solution using Kafka for ingestion, Apache Storm for continuous computation, and various storage options, while also covering streaming concepts and Storm's high‑availability mechanisms.

Apache StormKafkaReal-time Computing
0 likes · 8 min read
Real-Time Computing with Apache Storm: Architecture, Code Samples, and Fault Tolerance

Designing a Business‑Oriented High‑Availability Architecture for Game Access Systems

The article presents a comprehensive, business‑centric high‑availability architecture for a game access platform, detailing measurable goals, a three‑layered design, client‑side retry with HTTP‑DNS, functional separation and degradation, multi‑region active‑active deployment, and automated, visual monitoring to achieve rapid issue detection, recovery, and minimal downtime.

business reliabilitydistributed systemsfault tolerance
0 likes · 23 min read
Designing a Business‑Oriented High‑Availability Architecture for Game Access Systems
21CTO
21CTO
Oct 12, 2015 · Databases

How NoSQL Databases Achieve Scalability: Distributed Strategies Explained

This article systematically explores the distributed characteristics of NoSQL databases, covering data consistency, placement, peer systems, anti‑entropy protocols, eventual consistency data types, sharding, fault detection, and coordinator election, illustrating how these strategies balance scalability, availability, latency, and fault tolerance.

NoSQLReplicationfault tolerance
0 likes · 33 min read
How NoSQL Databases Achieve Scalability: Distributed Strategies Explained

Understanding Storm: A Distributed Real-Time Computation System

The article explains the need for low‑latency, high‑performance, distributed real‑time processing, outlines the challenges such systems must address, and introduces Storm as a Hadoop‑like framework for stream processing, detailing its architecture, fault‑tolerance mechanisms, transactional topology, and large‑scale deployment at Taobao.

Stormbig datadistributed systems
0 likes · 14 min read
Understanding Storm: A Distributed Real-Time Computation System
21CTO
21CTO
Sep 19, 2015 · Artificial Intelligence

Why Distributed Machine Learning Needs More Data Than Speed

The article explains how distributed machine learning evolved from parallel computing to handle massive, long‑tail data sets, discusses the importance of scalability, fault recovery, and data‑parallel algorithms, and reviews frameworks such as MPI, MapReduce, and Pregel for building large‑scale AI systems.

LDAMPIMapReduce
0 likes · 24 min read
Why Distributed Machine Learning Needs More Data Than Speed
21CTO
21CTO
Aug 29, 2015 · Backend Development

How to Prevent Service Failures: Trust Third‑Party, Guard Users, Master Your Own Code

An experienced backend engineer shares practical strategies to prevent service failures, covering third‑party distrust, user‑side safeguards, robust API design, traffic limiting, resource management, and architectural best practices such as single‑responsibility and avoiding single points of failure.

API DesignSingle Responsibilityfault tolerance
0 likes · 16 min read
How to Prevent Service Failures: Trust Third‑Party, Guard Users, Master Your Own Code
Qunar Tech Salon
Qunar Tech Salon
Aug 16, 2015 · Fundamentals

Key Characteristics and Design Principles of Distributed Systems

The article explains the historical background, core characteristics such as scalability, cost‑efficiency, fault tolerance, and elasticity, and outlines essential design principles for distributed systems, emphasizing low hardware requirements, horizontal scaling, avoidance of single points of failure, reduced communication overhead, and stateless services.

Horizontal ScalingStateless Servicesfault tolerance
0 likes · 12 min read
Key Characteristics and Design Principles of Distributed Systems
Hulu Beijing
Hulu Beijing
Aug 14, 2015 · Big Data

How Voidbox Bridges Docker and YARN for Scalable Big Data Workloads

Voidbox integrates Docker containers with YARN to simplify distributed application development, improve deployment, boost cluster efficiency, and provide fault‑tolerant, DAG‑based execution modes, enabling seamless resource management for Hadoop‑based big data jobs.

Cluster ComputingDAGDocker
0 likes · 17 min read
How Voidbox Bridges Docker and YARN for Scalable Big Data Workloads
Architect
Architect
Jul 22, 2015 · Backend Development

Using an API Gateway in a Microservices Architecture

The article explains how an API Gateway can consolidate multiple fine‑grained microservice endpoints into a single coarse‑grained API for mobile clients, discussing its design considerations, benefits, drawbacks, and implementation techniques such as reactive programming, service discovery, and fault tolerance.

API GatewayReactive ProgrammingService Discovery
0 likes · 13 min read
Using an API Gateway in a Microservices Architecture
High Availability Architecture
High Availability Architecture
Jul 22, 2015 · Backend Development

Designing Uber’s High‑Availability Messaging System: Fault Tolerance, Sharding, and Multi‑Data‑Center Strategies

The article details Uber senior engineer Zhao Lei’s presentation on building a highly available messaging platform, covering single‑point failure mitigation, sharding approaches, large‑scale outage handling, cross‑region failover, and the practical engineering practices and protocols used to keep billions of users online.

BackendHigh Availabilityfault tolerance
0 likes · 16 min read
Designing Uber’s High‑Availability Messaging System: Fault Tolerance, Sharding, and Multi‑Data‑Center Strategies

Key Characteristics and Design Principles of Distributed Systems

Distributed systems, long used since the 1970s and popularized by internet giants like Google, offer scalable, cost‑effective, and fault‑tolerant architectures by leveraging many low‑cost servers, emphasizing horizontal scaling, avoidance of single points of failure, minimal inter‑node communication, and stateless services for elastic application deployment.

Horizontal ScalingStateless Servicesdistributed systems
0 likes · 13 min read
Key Characteristics and Design Principles of Distributed Systems
Qunar Tech Salon
Qunar Tech Salon
May 21, 2015 · Fundamentals

Key Characteristics and Design Principles of Distributed Systems

The article explains the origins, core features such as scalability, cost‑effectiveness, fault tolerance, and elastic expansion of distributed systems, and outlines design philosophies like low hardware requirements, horizontal scaling, avoidance of single points of failure, minimized inter‑node communication, and stateless service architecture.

Horizontal ScalingStateless Servicesdistributed systems
0 likes · 11 min read
Key Characteristics and Design Principles of Distributed Systems