Ticket server

Flickr-style central auto-increment id server.

Provider: default
Kind: ID generator
Category: Data
Official docs: https://en.wikipedia.org/wiki/Auto-increment

Properties · 5 set by this component

property	type	values	required	kind default	this component
backingStore · component property	ref	—	no	—	inherited
batchSize	integer	—	no	—	inherited
central	boolean	—	no	false	▸ true
clockRollbackGuard · advanced	boolean	—	no	false	▸ false
interleaveStep · component property	integer	—	no	1	inherited
managed	boolean	—	no	false	inherited
replicated	boolean	—	no	false	▸ false
strategy	enum	uuid \| ulid \| snowflake \| counter \| counter-batched \| hash	yes	—	▸ counter
timeSortable	boolean	—	no	false	▸ true

Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.

Use it in a design

nodes:
  - { id: "ticket-server", component: "ticket-server" }

Other ID generator products · 4

Generic ID generatorid-generatorid-generator Snowflake IDsnowflake-idid-generator ULID serviceulid-serviceid-generator UUID generatoruuid-generatorid-generator

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Flickr-style ticket server: a central auto-increment row handing out ids; pairing two servers
3# on odd/even sequences is how it is replicated.
4schemaVersion: "1"
5type: "component"
6id: "ticket-server"
7kind: "id-generator"
8provider: "default"
9docs: "https://en.wikipedia.org/wiki/Auto-increment"
10defaults:
11  strategy: "counter"
12  central: true
13  replicated: false
14  timeSortable: true
15  clockRollbackGuard: false
16properties:
17  backingStore:
18    type: "ref"
19    refKind: "sql-database"
20  interleaveStep:
21    type: "integer"
22    default: 1

The same page as markdown, for an agent: /catalogue/components/ticket-server.md