BestHub
Sign in
Tagged articles

distributed-id-generation

4 articles · Page 1 of 1
Top Architect
Top Architect
Oct 13, 2026 · Backend Development

Snowflake ID Collision in Production: Why Custom ID Generators Fail

A production incident caused by a flawed custom Snowflake ID generator with a 31-bit timestamp (24-day cycle), IP-based BusinessId collisions, and unconfigured WorkerId/DataCenterId led to duplicate order IDs; the article analyzes the root causes and recommends mature libraries like Hutool and Baomidou with proper WorkerId assignment strategies.

backend developmentbaomidoudistributed-id-generation
0 likes · 8 min read
Snowflake ID Collision in Production: Why Custom ID Generators Fail
Xiaolin Talks Programming
Xiaolin Talks Programming
Sep 4, 2026 · Backend Development

Spring Boot High-Concurrency Distributed ID Generation: Snowflake Algorithm, Clock Drift Handling & Performance Optimization

This article walks through implementing Twitter's Snowflake algorithm in Spring Boot for distributed ID generation, covering 64-bit structure, clock drift mitigation strategies (wait, error, historical compensation), pre-generated ID pools with double buffering for 120k QPS, MyBatis-Plus integration, and Meituan Leaf design insights.

MyBatis-Plusclock-driftdistributed-id-generation
0 likes · 17 min read
Spring Boot High-Concurrency Distributed ID Generation: Snowflake Algorithm, Clock Drift Handling & Performance Optimization
Yumin Fish Harvest
Yumin Fish Harvest
Aug 29, 2026 · Backend Development

CosId Distributed ID Generation: Snowflake & Segment Modes Explained

This article explores CosId's two ID generation modes—local computation (Snowflake) and segment allocation (SegmentId, SegmentChainId)—with detailed configuration for JDBC, Redis, ZooKeeper, MongoDB, and Proxy backends, plus Spring Boot, MyBatis, and ShardingSphere integration examples.

CosIdJDBCRedis
0 likes · 34 min read
CosId Distributed ID Generation: Snowflake & Segment Modes Explained
Alibaba Cloud Developer
Alibaba Cloud Developer
Feb 3, 2021 · Operations

How to Build True Multi‑Region Active‑Active Architecture with Bidirectional Sync

This article explains why true multi‑region active‑active requires data to be bidirectionally synchronized across three or more centers, and details a multi‑center disaster‑recovery architecture, distributed ID generation algorithms, CAP considerations, and techniques for achieving eventual consistency.

Data Synchronizationdisaster recoverydistributed systems
0 likes · 14 min read
How to Build True Multi‑Region Active‑Active Architecture with Bidirectional Sync