BestHub
Sign in
Tagged articles

Fault Tolerance

328 articles · Page 4 of 4
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.

Elastic ScalingFault Tolerancecache
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.

Fault ToleranceMicroservicesservice discovery
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.

DisqueFault ToleranceIn-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.

BulkheadFallbackFault Tolerance
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.

Big DataData ReplicationDistributed File System
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.

AlgorithmFault ToleranceRead/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.

Fault ToleranceOperationsbusiness‑centric design
0 likes · 22 min read
Building a 3‑Minute Fault Detection, 5‑Minute Recovery HA System for Games
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
Jul 14, 2016 · Operations

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.

Fault ToleranceMonitoringbusiness continuity
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.

Fault Toleranceconsistency
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.

Fault TolerancePaxosdistributed consensus
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.

Fault ToleranceOperationsdistributed systems
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.

Fault ToleranceOperationsSystem Design
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.

Fault ToleranceLoad BalancingRound Robin
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 GatewayFault ToleranceMicroservices
0 likes · 13 min read
Understanding Microservices: Concepts, Benefits, and Practical Implementation
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
Nov 9, 2015 · Operations

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.

Fault ToleranceMonitoringbusiness reliability
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.

Fault ToleranceNoSQLreplication
0 likes · 33 min read
How NoSQL Databases Achieve Scalability: Distributed Strategies Explained
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
Sep 25, 2015 · Big Data

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.

Big DataFault ToleranceStorm
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.

Big DataFault ToleranceLDA
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 DesignFault ToleranceSingle Responsibility
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.

Fault Tolerancehorizontal scalingscalability
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.

Big DataCluster ComputingDAG
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 GatewayBackend ArchitectureFault Tolerance
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.

Fault ToleranceHigh Availabilitybackend
0 likes · 16 min read
Designing Uber’s High‑Availability Messaging System: Fault Tolerance, Sharding, and Multi‑Data‑Center Strategies
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
Jun 13, 2015 · Fundamentals

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.

Fault Tolerancedistributed systemshorizontal scaling
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.

Fault Tolerancedistributed systemshorizontal scaling
0 likes · 11 min read
Key Characteristics and Design Principles of Distributed Systems
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
May 1, 2015 · Backend Development

What Makes Disque a Fault‑Tolerant Distributed Message Broker?

Disque, an open‑source distributed in‑memory message broker created by Redis's creator, offers synchronous replication, flexible delivery semantics, multi‑master clustering, and fine‑grained job control, but remains in Alpha with several limitations that make it unsuitable for production use today.

DisqueFault ToleranceMessage Broker
0 likes · 6 min read
What Makes Disque a Fault‑Tolerant Distributed Message Broker?