asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: add a section on heavy operations in loaders (#12749)

Browse Source
This commit is contained in:
Shahed Nasser
2025-06-16 17:38:45 +03:00
committed by GitHub
parent 48810faa96
commit f4b3528fb1
3 changed files with 34 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/book/app/learn/fundamentals/modules/loaders/page.mdx
+15
View File
@@ -116,6 +116,21 @@ Loaders are also executed when you run [migrations](../../data-models/write-migr
---
## Avoid Heavy Operations in Loaders
Since loaders are executed when the Medusa application starts, heavy operations will increase the startup time of the application.
So, avoid operations that take a long time to complete, such as fetching a large amount of data from an external API or database, in loaders.
### Alternative Solutions
Instead of performing heavy operations in loaders, consider one of the following solutions:
- Use a [scheduled job](../../scheduled-jobs/page.mdx) to perform the operation at specified intervals. This way, the operation is performed asynchronously and doesn't block the application startup.
- [Emit custom events](../../events-and-subscribers/emit-event/page.mdx) in an [API route](../../api-routes/page.mdx), then handle the event in a [subscriber](../../events-and-subscribers/page.mdx) to perform the operation asynchronously. You can then send a request to the API route to trigger the operation when needed.
---
## Example: Register Custom MongoDB Connection
As mentioned in this chapter's introduction, loaders are most useful when you need to register a custom resource in the module's container to re-use it in other customizations in the module.