Book Image

ASP.NET Core 5 for Beginners

By : Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price
Book Image

ASP.NET Core 5 for Beginners

By: Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price

Overview of this book

ASP.NET Core 5 for Beginners is a comprehensive introduction for those who are new to the framework. This condensed guide takes a practical and engaging approach to cover everything that you need to know to start using ASP.NET Core for building cloud-ready, modern web applications. The book starts with a brief introduction to the ASP.NET Core framework and highlights the new features in its latest release, ASP.NET Core 5. It then covers the improvements in cross-platform support, the view engines that will help you to understand web development, and the new frontend technologies available with Blazor for building interactive web UIs. As you advance, you’ll learn the fundamentals of the different frameworks and capabilities that ship with ASP.NET Core. You'll also get to grips with securing web apps with identity implementation, unit testing, and the latest in containers and cloud-native to deploy them to AWS and Microsoft Azure. Throughout the book, you’ll find clear and concise code samples that illustrate each concept along with the strategies and techniques that will help to develop scalable and robust web apps. By the end of this book, you’ll have learned how to leverage ASP.NET Core 5 to build and deploy dynamic websites and services in a variety of real-world scenarios.
Table of Contents (19 chapters)
Section 1 – Crawling
Section 2 – Walking
Section 3 – Running

Learning about monitoring and health

A misconception of how things work in the cloud is that the cloud provider handles the health of your app. We saw in the first part of this chapter the division of responsibility going from IaaS to SaaS, where the provider takes greater responsibility as you move to the right. If you go all the way to SaaS, it is true that the provider has to handle pretty much everything that isn't a user error, but as stated earlier, the sweet spot for developers is usually PaaS, where there is still some responsibility on your part.

This means that if the response time of a web app as experienced by the user is not acceptable, you need to be aware of this and figure out how to handle it. If storage in the cloud goes down, you need to understand how to remediate this. The you part here could be handled differently, depending on your organization, but in most instances, it is not the cloud provider that will be responsible, even if they have mechanisms...