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

Distributed caching

A distributed cache or global cache is a single instance or a group of cache servers with a dedicated network. As the applications hit the distributed cache, if cached data related to the application's request does not exist, the request redirects to the database to query the data. Otherwise, the distributed cache will simply respond with the data needed by the applications.

Here's a diagram of two servers sharing the same Redis instance for distributed caching:

Figure 10.1 – Distributed caching

The preceding diagram shows the requests from two servers hitting a Redis cache first before deciding whether to query from the database or not.

What happens if one of your services crashes? Nothing really because everyone is going to be querying the distributed cache anyway. And because the cache is distributed, it's going to be maintaining the data consistency. We can offload all that information and all that headache...