ChilliCream Training
Our GraphQL curriculum is designed to teach in depth and works really well. It also isn't set in stone, so we shape every engagement to the team in the room.
Where is your team today?
The curriculum is the same set of building blocks. The order, the depth, and the exercises change for the room.
Heard of GraphQL. Maybe shipped a toy server.
We start from REST instincts and rebuild them. By the end of week one your team can read a schema, write resolvers with confidence, and stop confusing fields with arguments.
What we cover
Half the team has shipped. Half the team is bluffing.
The most common shape we see. We split sessions into shared foundations plus parallel tracks, so nobody is bored and nobody is lost. Everyone leaves on the same page.
What we cover
Schemas in production. Now the corners get sharp.
For teams already shipping GraphQL who want to go deeper. We focus on the parts that hurt at scale: schema design, performance, federation with Fusion, and operating Hot Chocolate in anger.
What we cover
Two ways to run it
Both engagements use the same curriculum and the same trainers. They differ in how much hands-on project work sits at the end of the week.
Flexible curriculum, shaped to your team
Get your team trained in GraphQL, any of our products, and even React/Relay. Beginner Team? Advanced Team? Or Mixed? Don't panic! Our curriculum is designed to teach in-depth and works really well, but isn't set in stone.
What is in the box
Hands on, with a real project at the end
We will look at how to build a GraphQL server with ASP.NET Core 7 and Hot Chocolate. You will learn how to explore and manage large schemas. Further, we will dive into React and explore how to efficiently build fast and fluent web interfaces using Relay.
What is in the box
By the end of the week
No certificate-printer outcomes. These are the things we expect every team to walk away able to do, regardless of where they started.
Your team can navigate a large GraphQL schema, recognise the common shapes, and explain why a type is modelled the way it is.
From simple fields to data loaders and pagination, with the patterns that scale instead of the snippets that bite later.
Fragments, variables, error handling, and a Relay or Apollo setup that the next person on the team can actually maintain.
Open a trace, read the plan, find the N+1, and know which knobs to turn in Hot Chocolate before reaching for hacks.
When to split a schema, when not to, and how Hot Chocolate Fusion fits with the platform they already run.
Backend, frontend, and platform engineers leave with one shared vocabulary, so the next design review is faster and friendlier.
Delivery format
We have run training in all three formats. Pick the one that fits your calendar and your office, not the other way around.
A trainer joins your team in a room with a whiteboard and proper coffee. Best when you want the focused energy of being out of inboxes for a week.
Best for a single co-located team that can clear the calendar.
Live sessions over your call tool of choice, with shared notebooks, breakout rooms, and homework between days so timezones do not become a wall.
Best for distributed teams or when travel does not make business sense.
Deliberate breakout design and exercises that work for the people in the room and the people on the call, with a good A/V setup so nobody is half-present.
Best when part of the team can fly in and part cannot.
Training that nobody enjoys does not stick. We run sessions like the workshops we wish we had been to: hands on, slightly informal, no slide marathons, room for questions that start with “this is probably stupid but...” (it is not).
Common questions
Send a short note with the rough team size, current GraphQL level, and a couple of dates that work. We will reply with a concrete proposal, not a form to fill in.