Packages
ash_oban
0.8.9
0.8.10
0.8.9
0.8.8
0.8.7
0.8.6
0.8.5
0.8.4
0.8.3
0.8.2
0.8.1
0.8.0-rc.1
0.8.0-rc.0
0.7.2
0.7.1
0.7.0
0.6.0
0.5.1
0.5.0
0.4.12
0.4.11
0.4.10
0.4.9
0.4.8
0.4.7
0.4.6
0.4.5
0.4.4
0.4.3
0.4.2
0.4.1
0.4.0
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.6
0.2.5
0.2.4
0.2.3
0.2.3-rc.1
0.2.3-rc.0
0.2.2
0.2.1
0.2.0
0.1.14
0.1.13
0.1.12
0.1.11
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
The extension for integrating Ash resources with Oban.
Current section
Files
Jump to
Current section
Files
usage-rules/best_practices.md
<!--
SPDX-FileCopyrightText: 2020 Zach Daniel
SPDX-License-Identifier: MIT
-->
# Best Practices
1. **Always define module names** - Use explicit `worker_module_name` and `scheduler_module_name` to prevent issues when refactoring.
2. **Use meaningful trigger names** - Choose clear, descriptive names for your triggers that reflect their purpose.
3. **Handle errors gracefully** - Use the `on_error` option to define how to handle records that fail processing repeatedly.
4. **Use appropriate queues** - Organize your jobs into different queues based on priority and resource requirements.
5. **Optimize read actions** - Ensure that read actions used in triggers support keyset pagination for efficient processing.
6. **Design for idempotency** - Jobs should be designed to be safely retried without causing data inconsistencies.