Architecture

One hotel. Three JSONs.

Every hotel supplier speaks its own dialect.

What you'll learn

  • Why supplier JSON cannot be shown to travellers as it arrives
  • How one adapter per supplier and a canonical model fix prices and units
  • How a master hotel ID and a time budget fix duplicates and slow search
Design Pattern 10 steps 57 seconds —views

Was this useful?

Share

Understand it one step at a time

The short runs these in order in about 57 seconds. Here they are written out — pick any step to jump the short straight to it.

1 Step 1 of 10

Three suppliers, three JSONs

The same room, described three ways: per night, in paise, in dollars.

Free app · no app store

These are built for a phone

Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.

How it works

More shorts

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

↑↓ navigate ↵ open