Book Image

Building RESTful Web Services with .NET Core

By : Gaurav Aroraa, Tadit Dash
Book Image

Building RESTful Web Services with .NET Core

By: Gaurav Aroraa, Tadit Dash

Overview of this book

REST is an architectural style that tackles the challenges of building scalable web services. In today's connected world, APIs have taken a central role on the web. APIs provide the fabric through which systems interact, and REST has become synonymous with APIs. The depth, breadth, and ease of use of ASP.NET Core makes it a breeze for developers to work with for building robust web APIs. This book takes you through the design of RESTful web services and leverages the ASP.NET Core framework to implement these services. This book begins by introducing you to the basics of the philosophy behind REST. You'll go through the steps of designing and implementing an enterprise-grade RESTful web service. This book takes a practical approach, that you can apply to your own circumstances. This book brings forth the power of the latest .NET Core release, working with MVC. Later, you will learn about the use of the framework to explore approaches to tackle resilience, security, and scalability concerns. You will explore the steps to improve the performance of your applications. You'll also learn techniques to deal with security in web APIs and discover how to implement unit and integration test strategies. By the end of the book, you will have a complete understanding of Building a client for RESTful web services, along with some scaling techniques.
Table of Contents (13 chapters)

Summary

Registration is a very common, yet very important part of an application. We handled the registration of Customers through the API. Before that, we learned to bootstrap the API controller actions and model classes with EF Core. While we were doing all this, we landed on CORS and learned how to handle that, too.

Gradually, we moved to the authentication part, where we discussed Basic Authentication in detail. It is a mechanism to validate the client by the Customer (who are users of our API) credentials (username and password), which are passed in with the requests.

Bearer or Token-based Authentication was the next topic we explored, and we implemented the OAuth paradigm using IdentityServer4. In this case, the client can't access a resource directly by username and password as it was in the case of basic. What it needs is a token first, which is generated by one Authorization...