6 Components for Messaging and Caching

 

This chapter covers

  • The fundamental concepts of message queues and message brokers.
  • Integrating message brokers like RabbitMQ and Azure Storage Queues with .NET Aspire.
  • The fundamentals of distributed cache and using distributed locking for thread safety.
  • Using Redis to implement both distributed locking and caching.
  • Enabling the Redis management platform in Aspire.

It’s very common for distributed applications to have independent, self-contained services that communicate with each other using message brokers.

A message broker is a software system that mediates communication between applications, services, or microservices, enabling them to exchange information without being directly connected. It helps by managing the sending, receiving, and routing of messages between systems, which is especially useful in distributed architectures where services often need to communicate asynchronously.

Typically, this functionality is facilitated via messaging queues. This is when a service posts a message on a queue without knowing (or even caring) where it will end up. Another service subscribes to this queue. This receiver service reads the messages from the queue in the same order as they come.

6.1 Working with RabbitMQ

6.1.1 Hosting a RabbitMQ component

6.1.2 Sending messages via RabbitMQ

6.1.3 Consuming RabbitMQ messages

6.2 Working with Azure Queue Storage

6.2.1 Hosting an emulated Azure Queue Storage component

6.2.2 Sending messages via Azure Queue Storage

6.2.3 Consuming Azure Queue Storage messages

6.3 Overview of distributed cache and lock

6.4 Setting up Redis for caching and locking

6.4.1 Installing a Redis Component

6.4.2 Installing the Redis client for distributed caching

6.4.3 Using a distributed cache

6.4.4 Using a distributed lock

6.5 Calling the API

6.6 Managing Redis cache

6.7 Summary