danLeBrown

Tech Spec: Multi-Channel Notification System

Table of Contents

1. Overview
2. Goals & Non-Goals
3. Reliability Guarantees
4. Schema Design
5. System Architecture
6. End-to-End Flow

danLeBrown

Queues implementation using Bull JS & Redis

Introduction

Here are some of the identified suffixes for the keys you will find in Redis and the values they hold:

• :id - this key references the progression of the job ID. It is used to generate the next job ID
• :stalled-check - the time (probably of insertion) of the last stalled job
• :completed - the ids of completed jobs
• :failed - the ids of failed jobs

danLeBrown

This text now lives at https://github.com/MarcDiethelm/contributing/blob/master/README.md. I turned it into a Github repo so you can, you know, contribute to it by making pull requests.

---

Contributing

If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.

danLeBrown

// this is where alert data from the server is stored
const alertDataFromServer = []

// this is the message relayed to the user
const messageToPush = []

// res.data.data (alert data) comes from the server
alertDataFromServer.push(res.data.data)
alertDataFromServer.forEach((element) => {
  const errorObjects = element.errors.errors