Book Image

Hands-On Full-Stack Web Development with ASP.NET Core

By : Tamir Dresher, Amir Zuker, Shay Friedman
Book Image

Hands-On Full-Stack Web Development with ASP.NET Core

By: Tamir Dresher, Amir Zuker, Shay Friedman

Overview of this book

Today, full-stack development is the name of the game. Developers who can build complete solutions, including both backend and frontend products, are in great demand in the industry, hence being able to do so a desirable skill. However, embarking on the path to becoming a modern full-stack developer can be overwhelmingly difficult, so the key purpose of this book is to simplify and ease the process. This comprehensive guide will take you through the journey of becoming a full-stack developer in the realm of the web and .NET. It begins by implementing data-oriented RESTful APIs, leveraging ASP.NET Core and Entity Framework. Afterward, it describes the web development field, including its history and future horizons. Then, you’ll build webbased Single-Page Applications (SPAs) by learning about numerous popular technologies, namely TypeScript, Angular, React, and Vue. After that, you’ll learn about additional related concerns involving deployment, hosting, and monitoring by leveraging the cloud; specifically, Azure. By the end of this book, you’ll be able to build, deploy, and monitor cloud-based, data-oriented, RESTful APIs, as well as modern web apps, using the most popular frameworks and technologies.
Table of Contents (22 chapters)
Title Page
PacktPub.com
Contributors
Preface
Index

Making your APIs discoverable and self-documenting with the OpenAPI standard (Swagger)


When discussing Web APIs, you need to consider that the users that will interact with your API are developers, and not the end users of the product. The developers that use your API can use it in a variety of clients that can be written in various programming languages and technologies. Even though you created a REST API that uses standards such as HTTP and JSON, there are still things that are not standardized, such as the date-time format you use, numbers accuracy, and so on. Besides this, developers who want to use your API need a way to find out which data structures your API works with; what the URL structure is; what type of errors are returned from each action; and so forth. Then, the developer needs to put these definitions into code that can talk with your API, which can be a daunting task, especially when the API can change over time. You might even want to automate this task. To mitigate all...