Description
Hi Internet.nl team!
I'm working at The Swedish Internet Foundation and we are the registry for the .se zone. We have about 1,5M domain names that we plan to periodically check with the Internet.nl service.
We’ve set up our own instance of Internet.nl (including the batch API), and we have a few questions regarding a usage pattern that works very well in practice — but we’d like to confirm whether it’s officially supported or recommended.
What we’re doing
We start a large batch job (e.g., with 10,000 domains), which understandably takes some time to process. In parallel, we submit additional batch jobs — sometimes with only a single domain — and have observed that these smaller jobs are processed immediately and very quickly, without being queued behind the larger one.
This opens up the possibility of building our own interactive frontend where:
• a user submits a single domain,
• we create a new (small) batch job in the background,
• the frontend polls job status and displays the result.
In other words, we’re submitting single domains via the batch API, but only to our own private instance — not to the public service.
Our questions
1. Is this a supported and acceptable usage pattern, using the batch API with one domain per job, as long as it’s on our self-hosted instance?
2. Are there any technical risks or concerns when submitting many small jobs in parallel?
3. Is the setup guide in Docker-deployment-batch.md considered stable and suitable for production use?
4 Are there any recommendations or best practices you would suggest when running it in production?
Thank you for providing such an excellent and important tool for monitoring internet standards and resilience!
We look forward to your feedback.