# 21.04 Web API 300

> Independent deployability, for real: messaging, eventual consistency, event sourcing, and CQRS.

Format: 3 days · instructor-led
Builds on: 21.03

Every earlier course points at the same promise: services your team can change and deploy on its own schedule, without coordinating a release with five other teams. In practice, the promise usually breaks at the integration points: a shared database, a chain of synchronous calls, a message format nobody owns.

Web API 300 is where we keep it. We move integration from calls to events and messages, and deal honestly with what that costs: eventual consistency, delivery guarantees, idempotency, dead letters, outboxes and inboxes. Inside the service, we use event sourcing, CQRS, and the decider pattern to make business rules explicit, and project read models the rest of the system can use.

## Who it's for

Advanced C# developers who contribute to the design and architecture of service-oriented applications in .NET. Take [Web API 200](/21.03-web-api-200/) first, or bring equivalent experience designing and running HTTP APIs in production.

## How it runs

Three days, live and online, with the current release of .NET. Lecture, a lot of "code with me," and short practice exercises, plus two multi-hour labs where you put it together on your own. There's time every day for questions and one-on-one code review.

## What you'll be able to do

- Design services that deploy independently, and spot the coupling that prevents it.
- Integrate services with event streaming and messaging, choosing delivery guarantees on purpose.
- Handle messages idempotently, and use outboxes, inboxes, and dead letters to keep integrations resilient.
- Use an anti-corruption layer to keep another service's model from leaking into yours.
- Implement event sourcing in an API, and know when it's worth it.
- Model commands, events, and read models with CQRS and the decider pattern.
- Build read models with projections and snapshots, and stream changes to other services and UIs.
- Use feedback from tests, the pipeline, and OpenTelemetry to improve a service's reliability and performance.
