C4 model of a food-delivery platform
Who uses Forkway, the containers inside it, and the parts of its order and dispatch services.
Interactive maps, each built on a real model.
Drill in, step between states, and play a flow end to end.
29 maps
How systems are built and what they’re made of.
Who uses Forkway, the containers inside it, and the parts of its order and dispatch services.
A Rails monolith becomes five services over three years, drawn as C4 containers on one frame.
One drill through all four C4 levels: the system, its containers, the rate limiter, and the token bucket’s code.
A health plan’s prior-auth API through architecture review: its patterns, eight findings pinned in place and the conditions of approval.
Twenty-eight capabilities, the same grid by maturity and by spend, and the apps behind asset management.
Two credit unions’ 32 systems in one capability grid, stepped down to one system per capability by 2028.
A medical distributor’s systems and hubs: how each connection moves, a late stock file, and the move from SAP ECC to S/4HANA.
A hotel group’s lakehouse: RevPAR traced to its source columns, guest data by classification, and a legacy job’s impact.
The Purdue model in one frame: corporate IT, a DMZ with five conduits, and a bakery down to its burners.
Seven care agents: the data each can reach, who approved them, and the guardrails on credits and refunds.
A facade first, then one domain at a time: 1.4 million pension members move off a mainframe in three cohorts.
What an attacker can reach, and the controls that close it.
A payroll SaaS’s data flows, twelve STRIDE threats pinned where they strike, and the control that closes each.
Six findings on a digital bank’s Azure estate, and the controls that close them in place.
The paths into a research biotech’s crown jewels, the five-hop chain to cut first, and the fixes that close it.
How segmentation, P2PE and tokens shrink a cinema chain’s PCI scope from 20 systems to 6.
A FedRAMP Moderate boundary on AWS GovCloud: encrypted data flows, interconnections, who owns each control and the POA&M.
What one leaked credential reaches: a stolen laptop, a leaked CI token and a contractor nobody switched off.
How sites, devices and segments connect.
420 restaurants move from MPLS to SD-WAN and SASE, and the path from a store to Microsoft 365 gets shorter.
Five buildings on one core, every device by VLAN, and one closet down to its access points.
Four spines and a leaf pair per row, what one failed leaf takes down, and one rack slot by slot.
One network from L1 to L4: cables, VLANs, routes and ports, and the conduit both “redundant” uplinks share.
Where workloads run, and how they move.
Three waves move an outdoor retailer’s apps from Denver into AWS. Step through and watch each one cross.
An iron ore miner’s Azure estate: guardrails pinned where they apply, owners and cost, and a hub with one bypass.
A booking platform’s design, Terraform and Azure side by side: the drift a 2 a.m. hotfix left, and how it closed.
Regions, VPCs and subnet tiers on a transit gateway hub, with a lens on what the internet can reach.
How work moves through people and systems.
Six stages from first report to recovery, then down into evaluation and the offer, lane by lane.
What depends on what, and what happens when it breaks.
Clinical services down to the apps and infrastructure under them, and what fails when the storage array does.
A big on-sale minute by minute: the seat database saturates, a waiting room goes on, and sales recover.
Two Azure regions, what replicates, a failover rehearsal minute by minute and the five gaps it found.
No maps match these filters.
53 examples, from AWS architectures to data models and flowcharts.