mufassall

Business processes / 2 / 12

Money and rounding

A shop sells in so'm and issues e-invoices with 12% VAT. With prices as floating-point numbers, a payment of exactly the right amount fails an equality check. Amounts become integers in minor units with a currency, and then the real questions start: which rounding rule, where to round (per line or per invoice), how to split an amount without losing a tiyin, how to convert at a rate you can still prove a week later, and why formatting belongs only at the very edge.

  • 13 min
  • Intermediate
  • 12 steps
Difference, tiyin
0
Mismatched documents
0 /day
Refund shortfall, tiyin
0
Open in Lab

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

Numbers are a model scenario, not measurements

The real request

Checkout → Order service

Request

POST /v1/orders HTTP/1.1
Host: shop.example.com
Authorization: hidden

{
  "items": [
    { "sku": "TEA-250", "price": 119990.1, "qty": 23 }
  ],
  "total": 359970.3
}

Response

HTTP/1.1 201 Created
{ "order_id": "o_7714", "status": 4"awaiting_payment" }
  1. price — 19 990.10 so'm, sent as a JSON number, so it becomes a binary float.
  2. qty — A count: an integer, no problem here.
  3. total — Computed on the client and again on the server, both with floats.
  4. status — The order waits until a payment of exactly this total arrives.

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