What changes when your API moves to the edge?
Follow a catalogue request
A Brisbane reader opens a catalogue served from Sydney. An edge handler can return a cached public description nearby. If it then makes three sequential calls to Sydney for price, inventory and delivery, those round trips still sit on the critical path.
Separate the reads
Give public descriptions their own cache policy. Fetch customer-specific prices through an authenticated route. Keep stock reservations close to the database transaction that decides whether a unit is available.
Measure the whole journey
Compare warm and cold cache requests from the same client region. Record time to first byte, origin trips and the age of the data returned. A faster median can hide slower checkout requests.