You're reading from ASP.NET Core and Vue.js Build real-world, scalable, full-stack applications using Vue.js 3, TypeScript, .NET 5, and Azure

Product type Paperback

Published in Jun 2021

Publisher Packt

ISBN-13 9781800206694

Length 478 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Full Stack Web Development

Author (1):

Devlin Basilan Duldulao

View More author details

Table of Contents (25) Chapters

Preface

1. Section 1: Getting Started

2. Chapter 1: Getting Started with ASP.NET Core and Vue.js FREE CHAPTER

3. Chapter 2: Setting Up a Development Environment

4. Section 2: Backend Development

5. Chapter 3: Starting Your First ASP.NET Core Project

6. Chapter 4: Applying Clean Architecture to an ASP.NET Core Solution

7. Chapter 5: Setting Up DbContext and Controllers

8. Chapter 6: Diving into CQRS

9. Chapter 7: CQRS in Action

10. Chapter 8: API Versioning and Logging in ASP.NET Core

11. Chapter 9: Securing ASP.NET Core

12. Chapter 10: Performance Enhancement with Redis

13. Section 3: Frontend Development

14. Chapter 11: Vue.js Fundamentals in a Todo App

15. Chapter 12: Using a UI Component Library and Creating Routes and Navigations

16. Chapter 13: Integrating a Vue.js Application with ASP.NET Core

17. Chapter 14: Simplifying State Management with Vuex and Sending GET HTTP Requests

18. Chapter 15: Sending POST, DELETE, and PUT HTTP Requests in Vue.js with Vuex

19. Chapter 16: Adding Authentication in Vue.js

20. Section 4: Testing and Deployment

21. Chapter 17: Input Validations in Forms

22. Chapter 18: Writing Integration Tests Using xUnit

23. Chapter 19: Automatic Deployment Using GitHub Actions and Azure

24. Other Books You May Enjoy

When to use CQRS

Why would you want to use the mediator or the CQRS patterns? There are a lot of reasons for sure, but we will only go over the apparent reasons, which are as follows:

Services call each other: All the read and write requests go into the box in the middle (the mediator) and then come out. If you want to trigger any request from anywhere, the request has to hit the box in the middle, the mediator.
Clean code in large projects: The use of the mediator and mediator pipelines will help you shrink your controller sizes and move your business logic into their respective files. Hence, it will be effortless to traverse the folder structure and find the logic you're looking for.
A boundary between writes and reads: Any UI team can efficiently implement a UI that requires more data from the database due to the separation of reads and writes.
A UI team can work freely without worrying about affecting the backend work and how logic may distribute notifications...