bree VS bottleneck

If you only need a single instance, you can use Bree to handle your cron jobs without blocking your main thread.

Been using https://github.com/hexagon/croner and https://github.com/breejs/bree depending on the use case, both are currently being maintained.

Bree is another package with support for workers threads and cron syntax. But for the purpose of this article, we will stick to node-cron. So let's run a simple example:

For more advanced use cases, you might want to look into using a full-featured job queue instead like bree, bull, or agenda.

An impressive scheduling package I use is called Bree: https://github.com/breejs/bree

Bree is a super cool cron like scheduler that uses workers to run jobs https://github.com/breejs/bree

bottleneck

I tried to use the Bottleneck library to rate limit a script that needs to make a lot of calls to a 3rd party API in Deno. However, to my surprise it just has no effect, even when tested on small toy examples. I didn't try it in Node or the browser. Is there a reason why this library just wouldn't work on the Deno runtime? Is there a good alternative? It's a hard thing to google for because results tend to be either cron or server-side libraries.

If you have trouble with floods of traffic, use a rate limiter. Check out https://www.npmjs.com/package/bottleneck

Perhaps some streaming (native streams or some observables like rxjs) solution combined with rate limiting like https://www.npmjs.com/package/bottleneck ?

In general, you should avoid reinventing the wheel, so we looked for libraries which could solve our problem. We found BottleneckJS and decided to try to use it for our initial prototype.

Between tiny-async-pool and bottleneck I can suck data from any api very efficiently and within rate limits

Ah, this looks really nice! https://www.npmjs.com/package/bottleneck

As we can see here, in order to not violate the rate limiting rule, we must have 5 attempts at the API per minute or wait at lease 200 milliseconds between the executions. This was not that hard, but wait, JavaScript is asynchronous in nature. How will we make it run synchronously and sequentially ? The real question we are actually asking is, how do we make it that the HTTP requests to the remote API will wait the minimum delay time in between the executions. This is where we are going to use the tool that is called BottleNeck.