Book Image

Hands-On RESTful Web Services with ASP.NET Core 3

By : Samuele Resca
Book Image

Hands-On RESTful Web Services with ASP.NET Core 3

By: Samuele Resca

Overview of this book

In recent times, web services have evolved to play a prominent role in web development. Applications are now designed to be compatible with any device and platform, and web services help us keep their logic and UI separate. Given its simplicity and effectiveness in creating web services, the RESTful approach has gained popularity, and this book will help you build RESTful web services using ASP.NET Core. This REST book begins by introducing you to the basics of the REST philosophy, where you'll study the different stages of designing and implementing enterprise-grade RESTful web services. You'll also gain a thorough understanding of ASP.NET Core's middleware approach and learn how to customize it. The book will later guide you through improving API resilience, securing your service, and applying different design patterns and techniques to achieve a scalable web service. In addition to this, you'll learn advanced techniques for caching, monitoring, and logging, along with implementing unit and integration testing strategies. In later chapters, you will deploy your REST web services on Azure and document APIs using Swagger and external tools such as Postman. By the end of this book, you will have learned how to design RESTful web services confidently using ASP.NET Core with a focus on code testability and maintainability.
Table of Contents (26 chapters)
Free Chapter
1
Section 1: Getting Started
3
Section 2: Overview of ASP.NET Core
10
Section 3: Building a Real-World RESTful API
19
Section 4: Advanced Concepts for Building Services

What is a controller?

Controllers are the C part of the MVC pattern. They are a set of actions that usually handle requests from a client. You should bear in mind that what we are discussing in this chapter refers to the MVC stack that's defined by ASP.NET Core. Furthermore, if we take as reference the incoming requests, remember that they have already passed through the others middleware in the middleware pipeline and that they have already hit the MVC middleware.

The following diagram shows how a request is typically handled:

As we discussed in Chapter 1, REST 101 and Getting Started with ASP.NET Core, the incoming request is usually generated by a client: the browser, another API, or an external system. The request is composed of an HTTP verb, a URI, body payload, and other additional information. The Routing engine handles the request and passes it to an action method...