Bootcamps
Coming soon · the subjects below are what they will draw on
Subjects
What it is
Compute, storage, networking and identity on a cloud provider, plus cost and availability design.
Where it sits
School of Cloud Computing · Upper level
Crunch AWS — Amazon Web Services Engineering
You get
Fifteen weeks on AWS as a platform discipline — compute, storage, networking, identity, cost control and a production-grade system you deploy, using the free tier, Spot and LocalStack so it stays affordable.
Crunch GCP — Google Cloud Engineering
You get
The same ground on Google Cloud, ending in a production-grade GKE-based system.
What it is
The layered model, IP and TCP, routing, DNS, HTTP, and diagnosing a network that is misbehaving.
Where it sits
School of Cloud Computing · Core
You get
Capturing and reading real traffic, the Linux networking stack audited, and the protocol behaviour that matters for defending a host.
Still to add
Networking as its own subject — the layered model, routing, and congestion control.
Not ready yet · on the build list
What it will cover
A course of its own: the layered model, Ethernet and switching, IP addressing and subnetting, routing protocols, TCP and UDP behaviour under loss, DNS, TLS and HTTP, and packet-level debugging with a capture in front of you.
DM us to ask for it — requests decide the order
What it is
Pipelines, containers, infrastructure as code, observability, and releasing without downtime.
Where it sits
School of Cloud Computing · Upper level
You get
Containerising an application, orchestrating it, provisioning with infrastructure as code, building CI/CD pipelines, configuring observability, managing secrets, diagnosing a production issue, and shipping.
What it is
Consistency, replication, consensus, failure handling, and services that span many machines.
Where it sits
School of Cloud Computing · Upper level
Crunch Mesh — Microservices & Distributed Systems
You get
Distributed systems as a senior-to-staff engineer works them: service decomposition, messaging, consistency and replication, partial failure, observability, and the operational reality of many machines.
What it is
How organizations run on information systems: data, process, integration, and IT decision-making.
Where it sits
School of Cloud Computing · Intro
Crunch Information Systems — Intelligent Systems Design
You get
Seeing the whole system: requirements gathering, data modelling, querying and wrangling, process modelling and automation, enterprise systems, integration, and architecting for the cloud.
What it is
Caching, load balancing, sharding, queues, and the capacity reasoning behind a system that stays up.
Where it sits
School of Cloud Computing · Upper level
Crunch Mesh — Microservices & Distributed Systems
You get
Scaling decisions argued properly — caching, partitioning, queues, replication and the failure each one buys or costs.
Still to add
Measurement-led performance work — profiling, load testing and queueing analysis — rather than design reasoning alone.
You get
The system-design conversation as an interview asks it: capacity estimates, data model, bottlenecks and trade-offs, out loud.
What it is
Eliciting requirements, modelling process, specifying a system, and handing it to a build team.
Where it sits
School of Cloud Computing · Core
Crunch Information Systems — Intelligent Systems Design
You get
Requirements analysis and gathering, proper data modelling, process modelling and automation, and integration across enterprise systems.
Crunch Project Management — Agile Delivery for Tech Teams
You get
The delivery wrapper: scope, stakeholders, estimation and dependency management.