2da15ba021
* docs: added architecture documentation * update diagrams and text * address PR comments * sidebar + overview fixes
34 lines
1.5 KiB
Plaintext
34 lines
1.5 KiB
Plaintext
export const metadata = {
|
||
title: `${pageNumber} Architectural Modules`,
|
||
}
|
||
|
||
# {metadata.title}
|
||
|
||
In this chapter, you’ll learn about architectural modules.
|
||
|
||
## What is an Architectural Module?
|
||
|
||
An architectural 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.
|
||
|
||
---
|
||
|
||
## Architectural Module Types
|
||
|
||
There are different architectural module types including:
|
||
|
||
|
||
|
||
- Cache 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.
|
||
|
||
---
|
||
|
||
## Architectural Modules List
|
||
|
||
Refer to the [Architectural Modules reference](!resources!/architectural-modules) for a list of Medusa’s architectural modules, available modules to install, and how to create an architectural module.
|