Skip to content

Commit bf77419

Browse files
authored
chore: update readme (#63)
1 parent 0193ef3 commit bf77419

File tree

4 files changed

+9
-3
lines changed

4 files changed

+9
-3
lines changed

.github/workflows/codestyle.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
name: codestyle
22
on:
33
pull_request:
4+
paths:
5+
- "!*.md"
46
jobs:
57
code-coverage:
68
name: Code Coverage

.github/workflows/static-analysis.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ on:
66
- master
77
- '*.x'
88
pull_request:
9+
paths:
10+
- "!*.md"
911

1012
permissions:
1113
contents: read

.github/workflows/test.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
name: test
22
on:
33
pull_request:
4+
paths:
5+
- "!*.md"
46
jobs:
57
phptests:
68
runs-on: ${{ matrix.operating-system }}

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,14 +40,14 @@ Snowflake is a network service for generating unique ID numbers at high scale wi
4040
> You must know, The ID generated by the snowflake algorithm is not guaranteed to be unique.
4141
> For example, when two different requests enter the same node of the same data center at the same time, and the sequence generated by the node is the same, the generated ID will be duplicated.
4242
43-
So if you want to use the snowflake algorithm to generate unique ID, You must ensure: The sequence-number generated in the same millisecond of the same node is unique.
43+
If you want to use the snowflake algorithm to generate unique ID, You must ensure: The sequence-number generated in the same millisecond of the same node is unique.
4444
Based on this, we created this package and integrated multiple sequence-number providers into it.
4545

4646
* RandomSequenceResolver (Random)
47-
* RedisSequenceResolver (based on redis psetex and incrby)
47+
* FileLockResolver(PHP file lock `fopen/flock`, **Concurrency Safety**
48+
* RedisSequenceResolver (based on redis psetex and incrby, **Concurrency Safety**)
4849
* LaravelSequenceResolver (based on redis psetex and incrby)
4950
* SwooleSequenceResolver (based on swoole_lock)
50-
* FileLockResolver(PHP file lock `fopen/flock`
5151

5252
Each provider only needs to ensure that the serial number generated in the same millisecond is different. You can get a unique ID.
5353

0 commit comments

Comments
 (0)