callicoder / java-snowflake Goto Github PK

Hi - Planning to use this implementation for generating transaction Id for distributed system. Would like to understand how it generates unique number in different criteria.1. Sub-Nano second latency request. 2. Two request fired at the exact same time. 3. Distributed system generating the Same Id.

Was it tested and could you help with the test performed and the related details.

Hi,

Can you please update license to your repo?

Thanks

@callicoder The entire nextId() method is synchronized! Why do we need a volatile still?

private volatile long lastTimestamp = -1L;
private volatile long sequence = 0L;

public synchronized long nextId() {
}