CosIdUniversal, Flexible, High-Performance Distributed ID Generator

CosId 5: uniqueness that depends on no clock, one runtime for every strategy, one starter

Quick Start

Introduction

Migrating from 4.x

4.x docs

GitHub

🛡️

Unique by construction

A machine slot is leased as a time window: successive holders' windows never overlap, a rule kept inside the store. Clock skew, GC pauses and failovers cost availability, never uniqueness.

🌐

Every strategy

Snowflake (any Layout, milliseconds or seconds, JS-safe), the 80-bit CosId, segments that size themselves to a time budget, and periodic segments per year, month or day.

🧩

One runtime

Spring Boot, cosid-server and plain Java all start the same CosIdRuntime from one configuration model; stores are declared once and mixed freely.

🗄️

Five stores, one contract

JDBC (MySQL, MariaDB, PostgreSQL, SQL Server, H2), Redis, MongoDB, ZooKeeper and the remote server implement two primitives, verified by one TCK.

🚀

High performance

No lock and no I/O on the hot path: a segment id is one atomic add, a Snowflake id a short critical section. 5.0 is gated on matching 4.x in every benchmark.

📈

Observable

19 Micrometer meters, a health indicator for the slot lease, and an Actuator endpoint that describes and exercises every generator.

Preview

5.0.0-alpha.x is a preview with no compatibility promise. The API, configuration, storage format and cosid-server HTTP API may change between alphas and before GA, and no data migration is provided between alphas. Do not use it in production: stay on 4.x there (4.x docs).