mufassall

Business processes / 12 / 12

Gapless document numbering

In many countries issued invoices must carry continuous numbers: per series and per year, no number skipped and none used twice, and an auditor checks the register. A database sequence leaves gaps, MAX()+1 gives duplicates. A counter row taken in the finalize transaction gives both guarantees, at the price of making writers wait in line, so the lesson also measures that price and keeps it small.

  • 14 min
  • Intermediate
  • 12 steps
Missing numbers
0 /yr
Numbers used twice
0 /yr
Finalizes per series
900 /s
p99 finalize wait
4 ms
Open in Lab

  • request
  • reply
  • redelivery
  • duplicate
  • lost
  • call: the reply returns on the same line

Numbers are a model scenario, not measurements

The real request

Invoice service → Invoices DB

Request

INSERT INTO invoices (id, number, status, buyer_id)1
VALUES (gen_random_uuid(),
        'INV-2026-' || lpad(nextval('invoice_no')::text, 6, '0'),2
        'draft', 'b_310');3
-- the number is taken the moment a draft is created

Response

INSERT 0 1   number = INV-2026-0004814
  1. number — The legal identity of the document, printed on it and reported.
  2. nextval — A database sequence: fast, never blocks, never goes back.
  3. draft — The document is not issued yet, but it already holds a number.
  4. INV-2026-000481 — Series INV, year 2026, the 481st document of the year.

Build it yourselfCheat sheetCompare lessons

Course: 74 lessons
  1. 01 Foundations

    1. The life of a request
    2. Latency and throughput
    3. Napkin math
  2. 02 Scaling

    1. Scaling up vs scaling out
    2. Load balancing
    3. Stateless servers
    4. Caching
    5. Cache invalidation
    6. CDN and edge caching
  3. 03 Data & storage

    1. SQL and NoSQL
    2. Database indexes
    3. Geo search: who is nearby
    4. Full-text search
    5. Vector search
    6. Storage engines: B-tree and LSM
    7. Bloom filters
    8. Database replication
    9. Sharding
    10. Consistent hashing
    11. Unique IDs
    12. CAP: when the link breaks
    13. Consensus and leader election
    14. Transactions
    15. File uploads
  4. 04 Communication

    1. API styles
    2. Message queues
    3. Pub/sub and event logs
    4. Real-time updates
    5. Reliable callbacks
    6. Sending webhooks reliably
  5. 05 Reliability

    1. Redundancy and failover
    2. Rate limiting
    3. Timeouts and retries
    4. Observability
    5. SLOs and error budgets
    6. Backpressure
  6. 06 Architecture

    1. Microservices
    2. Service discovery
    3. Sagas and the outbox
    4. Change data capture (CDC)
    5. Transactional outbox
    6. Distributed locks
    7. Batch vs stream
    8. Multi-tenancy
    9. Event sourcing
  7. 07 Security

    1. Authentication
    2. Authorization
    3. Encryption and secrets
    4. Secrets management
  8. 08 Shipping

    1. Testing
    2. CI/CD: from commit to production
    3. Zero-downtime migrations
    4. Feature flags
  9. 09 Whole systems

    1. From requirements to design
    2. Design a URL shortener
    3. Design a news feed
    4. Design a chat
    5. Design a video streaming site
    6. Design search autocomplete
    7. Design a job scheduler
  10. 10 Business processes

    1. Payment gateway
    2. Money and rounding
    3. Double-entry ledger
    4. Payment reconciliation
    5. Subscription billing
    6. Electronic digital signature
    7. Document lifecycle
    8. Audit log
    9. Notification delivery
    10. Bulk import
    11. Refunds and chargebacks
    12. Gapless document numbering
  11. 11 Case studies

    1. Case: how Discord stores messages
    2. Case: Figma multiplayer editing