Hands-On RESTful Web Services with ASP.NET Core

I've gone through a lot of different .NET Web API books and most of them are confusing and not very complete. Sometimes I'll get lucky and find a good chapter about Web API in some .NET related book. For example, I found a good chapter about Web API in a .Net React book, but it wasn't as in-depth as this book (since it was only one chapter). This book is by far one of the better books covering all you need to know to start developing .NET Web API. It covers a lot of .NET Core concepts as well, which are needed for Web API. Because of this, it is a very complete book. I like that the author understands many of the intricacies of .NET and explains them in this book.I was confused about some of the bad ratings. I didn't see a lot of fluff in the book. Instead I saw a lot of valuable information. Maybe for someone who doesn't want to learn the small details might find this book overwhelming. But, if you want to be a good developer/programmer, you need to know the details. I've worked with too many developers who don't understand what they are doing and end up creating messy code.I highly recommend this book. I know .NET 6 is already out, but I couldn't find any newer books on Web API that I liked. So, I'm sticking with this one.

This book covers a lot of fairly advanced topics in less than 500 pages:- Middleware- Filters- Storing temporary (shopping cart) data using Redis- Resilience using Polly- Event bus using RabbitMQ- Distributed caching using Redis- HATEOAS- Swaggerin addition, of course, to standard concepts like Entity Framework with Repository Pattern, Unit Testing, JWT-based authorization, etc.The book also covers third-party tools and technologies, like Docker, Azure, Postman.So, sometimes you get a feeling that there is too much information crammed (many "advanced" books suffer from opposite problem - they try to explain in excruciating details even the most basic concepts). I could live without Repository pattern (IMHO, obsolete approach nowadays) and Azure deployment (we standardize on AWS). And with focus on Docker - there was no explanation how to deploy RabbitMQ or Redis without it. If you don't have prior experience - you will not get guidance from this book.But I understand that the author has to draw the balance somewhere - this may be perfect for somebody else. As they say, YMMV. Things that I learned about resilience in the chapter about Polly are perfect for me! The biggest downside for me is that from chapter 11 there is no way to actually run the code that we are developing!This book is clearly written by non-English native speaker... and would strongly benefit from a good technical editor. Some advanced topics are very difficult to understand because of that; and Chapter 15 indeed has a number of embarrassing errors. But overall, this is a book from which I learned a number of advanced skills and will refer to for months to come!NOTE to Amazon: book page shows that there are 3 reviews, but it only shows 1! Also, for some strange reason you do not allow comments on non-US reviews (probably for GDPR or some other weird reason). For the company that has AWS division that touts easing of GDPR compliance, this should be really embarrassing!

The exact material I was looking for...

This covers all topics needed to create web site in .NET. Nice definitions for routing which I found most useful

I know kind of a strange headline, but what I mean is this book has some good information in it, but it's strangely formatted and there is too much fluff in it. It led me to have to read and re-read certain parts thinking, "wait, why is the author taking the time to state something that is obvious, did I miss something!?". Also the subtitle of the book leads me to think this book is a professional reference, but really it's all demo code.The fluff - Chapter summary sections are ended with a summary of the chapter and a bit of information about the next chapter, and the next chapter starts with a summary of the previous chapter that I just read... fluff. This is 450+ pages book, I don't know why the author had to waste so many lines, just get to the points. I've got 5 other books to read.My biggest issue is with chapter 15, Securing APIs with token-based authentication starting page 372 all the way to the end of page 386. I don't even know what to say... Yes, the information is there, good luck making sense of it.If you have an electronic version of this book, can you let us know how many times the author uses the words: Therefore and furthermore? It's crazy!

I have 28 years of professional experience and have read thousands of books on software development. This one is clear and to the point. I am not sure why there are bad reviews, but perhaps it is because the book is not helpful for absolute beginners. You really do need to understand C# and .NET to jump into this book, but for any experienced developer, this book is the only book you need for ASP.NET Core RESTful services.

most of the PACKT book are poorly written and very badly organized books. this is the 3rd bad book from the publisher i encountered in the last 2 weeks and i returned all of them

Not well written, often the explanations are not clear..