bree - npm Package Compare versions

Comparing version 1.1.15 to 1.1.16

package.json

		{
		"name": "bree",
		"description": "The best job scheduler for Node.js with support for cron, dates, ms, later, and human-friendly strings. Uses workers to spawn sandboxed processes, and supports async/await, retries, throttling, concurrency, and cancelable promises (graceful shutdown). Simple, fast, and the most lightweight tool for the job. Made for Forward Email and Lad.",
		"version": "1.1.15",
		"version": "1.1.16",
		"author": "Nick Baugh <niftylettuce@gmail.com> (http://niftylettuce.com/)",
		@@ -6,0 +6,0 @@ "ava": {

README.md

		@@ -52,3 +52,3 @@ <h1 align="center">

		Previous to creating this, I was relying heavily on [bull][]; having created [@ladjs/bull][] – but due to core issues (and being Redis-backed) it was not the best tool for the job. [Bull][] might have been okay if the core issues were fixed, however since it uses [Redis][] it should not be used for a job queue. From my experience, [Redis][] should only be used for caching and session storage purposes (e.g. CDN or managing user log in state in your application).
		Previous to creating this, I was relying heavily on [bull][]; having created [@ladjs/bull][] – but due to core issues (and being Redis-backed) it was not the best tool for the job. [Bull][] might have been okay if the core issues were fixed, however since it uses [Redis][] it should not be used for a job queue. From my experience, [Redis][] should only be used for caching and session storage purposes (e.g. CDN or managing user log in state in your application). As of the time of this writing, it has been months and the core bugs with Bull are still unresolved; as more people are continuing to reproduce and comment on the known issues.

		@@ -55,0 +55,0 @@ Since [workers][] are now readily available in LTS versions of Node, I thought it would be a great time to implement them in a job scheduler environment. Additionally, my research and development of a better anti-spam and anti-phishing classifier with [Spam Scanner][spam-scanner] gave me some necessary insight to using [workers][].

New alerts