DQE One server is already available on Heroku Element Marketplace.
Warning: The DQE One server is required only for batch processing. If your scope involves Real-Time API usage only, the DQE One server is not needed.
Sizing requirements
| Type process | DQE One Server - Web (Mandatory for all plans) | Number of records and Dyno plan | Number of records and redis plan | Rabbitmq | Postgre |
| Batch (unify) |
1 dyno Standard 1X (1 dyno = 1 unit) |
500K = Performance M 2.5go (1 dyno = 8 units) 1 M = Performance M 2.5go (1 dyno = 8 units) 5 M = Performance L 30go (1 dyno = 16 units) 10 M = Performance L 30go (1 dyno = 16 units) 20 M = Performance XL 62go (1 dyno = 30 units) 40M = Performance 2XL 126go (1 dyno = 60 units) |
Plan Premium 0 | Free | No need |
| Batch (unify) + Lookup |
1 dyno Standard 2X (1 dyno = 2 unit) |
500K = Performance M 2.5go (1 dyno = 8 unit) 1 M = Performance M 2.5go (1 dyno = 8 unit) 5 M = Performance L 30go (1 dyno = 16 unit) 10 M = Performance L 30go (1 dyno = 16 unit) 20 M = Performance XL 62go (1 dyno = 30 units) 40M = Performance 2XL 126go (1 dyno = 60 units) |
For Batch: Plan Premium 0 For Lookup: 500K = Premium 5 1 M = Premium 5 5 M = Premium 7 10 M = Premium 10 |
Free | Essential 0 |
Sizing example
Example: 8M records in Batch + Lookup.
Context:
- DQE One Server - Web : 2 units
- Batch : 16 units
- Lookup : Premium 10 Redis
Result : 2 + 16 = 18 units with a Premium 10 Redis Plan
Related to