154673f3d8
* docs: changes based on DX changes * remove fields no longer needed * remove unnecessary parameters * fixes to authenticate middleware usage * add highlight to migrations config * change configuration to http * added missing remote link docs * fix name in sidebar * added notification module docs + updated file module docs * add vale exceptions * fix vale errors * added docs on custom cli scripts
28 lines
847 B
Plaintext
28 lines
847 B
Plaintext
import { ChildDocs } from "docs-ui"
|
||
|
||
export const metadata = {
|
||
title: `Event Modules`,
|
||
}
|
||
|
||
# {metadata.title}
|
||
|
||
An Event Module implements the underlying publish/subscribe system that handles queueing events, emitting them, and executing their subscribers.
|
||
|
||
This makes the event architecture customizable, as you can either choose one of Medusa’s event modules or create your own.
|
||
|
||
---
|
||
|
||
## List of Event Modules
|
||
|
||
By default, Medusa uses the Local Event Module. This module uses Node’s EventEmitter to implement the publish/subscribe system.
|
||
|
||
This is useful for development. However, for production, it’s highly recommended to use other Event Modules, Redis Event Module.
|
||
|
||
<ChildDocs type="item" filters={["Guides"]} onlyTopLevel={true} />
|
||
|
||
---
|
||
|
||
## Create a Event Module
|
||
|
||
To create an event module, refer to [this guide](./create/page.mdx).
|