zeplo.to/
to queue the request.GET
request to anyurl.com
, if response status code >=400
retry the request up to 3 times.Redis memory size and AWS permissions are annoying. With Zeplo you don't need to manage job state, queues, or workers.
You already have a HTTPS API, so creating a second interface and API for every service and method to make it asynchronous adds duplication and complexity.
The consumer service no longer needs to know whether it will be called async or sync. It’s the publishing/calling service that gets to decide.
Schedule a job to run after a given time, or at regular intervals (CRON, time or RRULE).
Specify how many times to retry the request before failing, with customizable backoff.
Every job is traced, including all headers and body for enhanced debugging
Auto-handles rate limit response headers, automatically retrying after the requested backoff
Fix and reprocess failed records in the console to ensure your jobs are always completed.
Push multiple jobs to the queue at once, ensuring transaction safe queueing.
Every job is logged in the Zeplo console, allowing you to see exactly what’s happening in your queue and to respond to any problems.
Cut above the noise and get alerts when things aren’t right. Setup custom alert filters and get notified by e-mail, Slack or PagerDuty.
Every job is logged in the Zeplo console, allowing you to see exactly what’s happening in your queue and to respond to any problems.
uptime
requests / month