Seneca’s Open Source Orbit: Telescope

Anton Biriukov
Dec 10, 2019 · 2 min read

As Seneca’s Telescope continues its development, more and more challenges are faced. For this week I have chosen to work on the database part of the application, specifically on the Redis constructor for the Bull queue. Let’s get started!

Photo by Cole Winters on Unsplash

Realizing the Goal

First of all, what is Bull and why do we need a queue? Well, Bull is a popular Open Source library providing a Redis-based queue for Node. In Telescope, it used to line up the feed of blogposts fetched from various blogging platforms. Originally, it was set up in the following way:

function createQueue(name) {
const log = logger.child({ module: `queue:${name}` });
const queue = new Bull(name, {
createClient: type => {
switch (type) {
case 'client':
return client;
case 'subscriber':
return subscriber;
return new Redis(redisUrl);
// ...


As you can see, the Redis data store is created with using only url. One of the downsides of such a solution is the lack of security. Of course, Redis comes up with a number of options for you on how to construct the database. After browsing the docs, I have found the following. The Redis object can be constructed as new Redis([port], [host], [options]), with options including password.


Therefore, in order to use this constructor, we needed to do a number of things:

  1. Parse port and host from the RedisUrl
  2. Add password property to the config file

The first step can be easily achieved by using the Node’s url.parse method:

const { port, host } = url.parse(redisUrl, true);

For the second step we just set up the prototype for the config file:


Afterwards, we need to create function which would do all of the work for us, including the error handling:

function createRedisClient() {
try {
const { port, host } = url.parse(redisUrl, true);
return new RedisConstructor(port, host, { password: process.env.REDIS_PASSWORD });
} catch (err) {
const message = `Unable to parse port and host from "${redisUrl}"`;
logger.error({ err }, message);
throw new Error(message);

Lastly, we just export our function through module.exports.


After a round of tests and improvements the code started to work as expected. The update has now been introduced to the project through a PR.We can now specify a secure connection to our Redis database!

More From Medium

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade