Kue without Redis

I'm running an app that (for the foreseeable future) will not be scaled beyond a single running instance. I'd like to keep the job queue in-memory without having to make calls to redis. Am I crazy or is kue unnecessary in this case?

I like the API a whole lot.

Thanks.

No files, tests, or entry points are named. Start by tracing how Kue initializes and uses Redis, then determine whether an in-memory single-process backend fits the existing API and what behavior would need tests before defining the scope.

Written by the indexing model from the issue text.