Building RESTful Web Services with .NET Core: Developing Distributed Web Services to improve scalability with .NET Core 2.0 and ASP.NET Core 2.0

by Gaurav Aroraa, Tadit Dash

Building Complete E-commerce/Shopping Cart Application 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. This book is intended for those who want to learn to build RESTful web services with the latest .NET Core Framework. To make best use of the code samples included in the book, you should have a basic knowledge of C# and .NET Core.

Genres: Programming

334 pages, Kindle Edition

Published May 31, 2018

Reviews

[Adam · Rating 1 out of 5]

Perfect example of a horrible technical book. I actually read the first few chapters multiple times thinking I was dense or missing something. Soon I realized the author never actually tells you anything. Sentences such as, "The term communication is self-explanatory." litter this book. The final chapters spewing nonsense and references to other sources for real meaning, had me thinking I'm asking for my money back from Packt. What a pile of garbage. Editor should be fired too.

Side note, I don't normally write bad reviews. I just think potential readers should be warned. If you don't believe me, read page 301, How a microservice works.

[José · Rating 2 out of 5]

the examples are confusing.