0 views collected around this technical thread.
This article explains MongoDB's three cluster architectures—deprecated Master‑Slave replication, the highly available Replica Set with automatic failover, and horizontal scaling Sharding—detailing their roles, data flow, advantages, limitations, and operational considerations for building reliable, scalable databases.
This article provides a concise, concept‑level overview of Kubernetes architecture, explaining the roles of master and worker nodes, Pods, networking, scheduling, storage, services, scaling, and controller interactions, illustrated with diagrams to help beginners grasp the system’s complexity.
This article explains Elasticsearch's cluster architecture, including nodes, indices, shards, and replicas, compares mixed and tiered deployment models, discusses the data storage layer and replication trade‑offs, and presents two typical distributed data system designs with their advantages and drawbacks.
This comprehensive guide introduces ClickHouse as a high‑performance columnar DBMS, outlines its typical OLAP use cases, explains the four families of table engines with detailed MergeTree variants, provides SQL creation syntax, shares development and write best practices, and describes cluster architecture, Zookeeper role, chproxy, client tools, availability considerations, and key configuration parameters.
This article explains Elasticsearch’s cluster and data layer architecture, covering nodes, indices, shards, replicas, mixed and tiered deployment models, storage options, and the trade‑offs of different distributed system designs for scalable systems.
This article explains Kafka’s core design concepts—including the role of a message system, topics, partitions, producers, consumers, consumer groups, replica management, controller coordination with Zookeeper, performance optimizations like sequential writes and zero‑copy, and its network thread model—illustrated with diagrams and code snippets.
This article introduces Elasticsearch as a distributed, high‑performance search engine, explains its cluster architecture, node roles, shard and replica mechanisms, write and refresh processes, and outlines search handling techniques such as pagination, scroll and search‑after with practical curl examples.
This article explains the core concepts of Elasticsearch—including nodes, indices, shards, and replicas—covers its cluster and data‑layer architectures, compares mixed and tiered deployment models, and discusses the advantages and drawbacks of replica‑based distributed storage systems.
This article explains the architecture of Elasticsearch clusters, covering node roles, index, shard and replica concepts, deployment models, data storage mechanisms, and compares two distributed system designs—local‑file‑system and shared‑file‑system—highlighting their advantages and trade‑offs.
This article provides a concise, question‑driven overview of Kubernetes, explaining the roles of master and node components, pod networking, scheduling, storage, service exposure, scaling, and controller interactions, while summarizing the essential objects and processes that power a cloud‑native cluster.
This article describes how to design and build a native distributed cluster called MyCluster without using any existing frameworks, covering master‑slave architecture, leader election, split‑brain handling, centralized configuration management, custom communication protocols, state transitions, and client interfaces.
This article explains Pika’s native distributed cluster architecture, detailing its deployment structure, data distribution with tables and slots, request processing flow, both non‑consistent and Raft‑based log replication, and the enhanced metadata management that enables scalable, high‑availability storage beyond single‑node Redis limitations.
The article explains the background, architecture, data distribution, processing flow, replication mechanisms, and management features of Pika's native distributed cluster, detailing how Etcd, LVS, and RocksDB are used to achieve scalable, persistent Redis-compatible storage with table isolation and flexible slot replication.
The article details how JD.com's order center migrated its massive order query workload from MySQL to Elasticsearch, iteratively improving cluster isolation, node deployment, replica tuning, master‑slave redundancy, version upgrades, and data synchronization while addressing performance pitfalls such as deep pagination and FieldData usage.
This article details how JD.com’s order center migrated its Elasticsearch cluster from a basic, default‑configured setup to a highly available, dual‑cluster architecture with increased replicas, dedicated hardware, version upgrades, and optimized shard and pagination strategies to handle billions of documents and hundreds of millions of daily queries.
This article details how JD Daojia's order center migrated from a simple MySQL‑backed system to a high‑throughput Elasticsearch cluster, describing each architectural phase, performance tuning measures, dual‑cluster real‑time backup, version upgrades, data synchronization strategies, and the key pitfalls encountered such as deep pagination and FieldData memory issues.
This article details the progressive evolution of JD.com’s order center Elasticsearch cluster—from its initial default setup through isolation, replica optimization, master‑slave adjustments, and real‑time dual‑cluster backup—highlighting architectural decisions, scaling strategies, synchronization methods, and operational challenges encountered.
This article details the step‑by‑step evolution of the JD Daojia order‑center Elasticsearch cluster—from an initial loosely configured deployment to a real‑time dual‑cluster architecture with replica tuning, master‑slave adjustments, data‑sync strategies, and lessons learned about pagination, fielddata, and doc values—highlighting how each phase improved query throughput, stability, and scalability for billions of documents.
This article provides a comprehensive introduction to Kafka, covering its role as a messaging system, core concepts such as topics, partitions, producers, consumers, and messages, and then delves into the cluster architecture including replicas, consumer groups, controller coordination with Zookeeper, performance optimizations, log segmentation, and network design.
This article details how JD.com’s order center migrated its Elasticsearch cluster through multiple architectural stages—initial deployment, isolation, replica tuning, master‑slave adjustments, and real‑time dual‑cluster backup—while addressing data synchronization, scaling, and performance pitfalls to achieve high availability and query stability.