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)

Advantages of microservices

The following are some advantages of microservices:

  • You don’t have to invest to make the entire application scalable. In terms of a shopping cart, we could simply load balance the product search module and order-processing module while leaving less frequently used operation services such as inventory management, order cancellation, and delivery confirmation.
  • We can easily match an organization’s departmental hierarchies. With different departments sponsoring product development in large enterprises this can be a huge advantage.
  • As the code is already done in a way that it is not dependent on code from other modules with isolated functionality, if done right, then the chances of a change in one microservice affecting another microservice is very small.
  • Since the entire application is more like a group of ecosystems that are isolated from...