21.02
item · Curriculum / Services

Web API 100

Most enterprise APIs aren’t designed so much as accumulated. An endpoint gets added for one screen, another for a batch job, a third because the second didn’t quite fit, and a year later nobody can say what a resource is or why a call returns what it does. The decisions that make an API easy or miserable to live with get made early, and usually by accident.

This course makes them on purpose. We start with HTTP itself: the constraints it puts on a design, and why they’re worth taking seriously instead of working around. Then we build a real API with ASP.NET Core, one decision at a time: resources and representations, endpoints, dependency injection, validation, documentation, calls to other services, authentication and authorization, and the tests that let you keep changing it without breaking the people who depend on it.

Who it’s for

C# developers who are new to building HTTP APIs in .NET, or who’ve been building them without ever being shown how. You should be comfortable with C# and Visual Studio. The free, self-paced Intro to Services with .NET is recommended pre-work, and covers the big picture this course builds on.

How it runs

Three days, live and online, with the current release of .NET. Short stretches of explanation, a lot of “code with me,” and practice exercises right after each idea while the questions are fresh. Two multi-hour labs give you time to 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

  • Explain what a resource is in your API, and why each endpoint returns what it returns.
  • Build endpoints with controllers or minimal APIs, and choose between them for a reason.
  • Use configuration and dependency injection without fighting service lifetimes.
  • Run the same API in development, test, staging, and production by changing configuration, not code.
  • Call other services with the HTTP client, and stay standing when they’re slow or down.
  • Secure an API with OpenID Connect, OAuth2, and authorization policies, and prove it with tests.
  • Evolve and version an API without breaking the clients that depend on it.
  • Write unit, integration, and system tests that keep the API safe to change.
  • Organize the project by feature (vertical slices) so a team can work in it without colliding.
21.02
Topics
21.02
Full topic list
Every topic in the course: for searching, and for checking against what your team needs.
→