export const metadata = { title: ${pageNumber} Infrastructure Modules, }

{metadata.title}

In this chapter, you’ll learn about Infrastructure Modules.

What is an Infrastructure Module?

An Infrastructure Module implements features and mechanisms related to the Medusa application’s architecture and infrastructure.

Since modules are interchangeable, you have more control over Medusa’s architecture. For example, you can choose to use Memcached for event handling instead of Redis.

---

Infrastructure Module Types

There are different Infrastructure Module types including:

• Analytics Module: Integrates a third-party service to track and analyze user interactions and system events.
• Caching Module: Defines the caching mechanism or logic to cache computational results.
• Event Module: Integrates a pub/sub service to handle subscribing to and emitting events.
• Workflow Engine Module: Integrates a service to store and track workflow executions and steps.
• File Module: Integrates a storage service to handle uploading and managing files.
• Notification Module: Integrates a third-party service or defines custom logic to send notifications to users and customers.
• Locking Module: Integrates a service that manages access to shared resources by multiple processes or threads.

<Note>

The Caching Module was introduced in Medusa v2.11.0 to replace the deprecated Cache Module.

</Note>

---

Infrastructure Modules List

Refer to the Infrastructure Modules reference for a list of Medusa’s Infrastructure Modules, available modules to install, and how to create an Infrastructure Module.