Skip to content

Latest commit

 

History

History
50 lines (38 loc) · 1.33 KB

README.md

File metadata and controls

50 lines (38 loc) · 1.33 KB
Raw

Description

Your task is to write a simple application server that prints a message at a given time in the future.

The server has only 1 API: [GET] "/printMeAt" - which receives two parameters, time and message, and writes that message to the server console at the given time. Since we want the server to be able to withstand restarts it will use Redis to persist the messages and the time they should be sent at. You should also assume that there might be more than one server running behind a load balancer (load balancing implementation itself does not need to be provided as part of the answer). In case the server was down when a message should have been printed, it should print it out when going back online.

The focus of the exercise is:

  • the efficient use of Redis and its data types
  • messages should not be lost
  • the same message should be printed only once
  • message order should not be changed
  • should be scalable
  • seeing your code in action (SOLID would be a plus)
  • docker would be a plus
  • tests would be a plus
  • use only redis

Installation

# in the root folder
$ yarn install
$ cp .env_default .env # set your parameters

Running the app

# development
$ yarn run start

# watch mode
$ yarn run start:dev

# production mode
$ yarn run start:prod

Test

# e2e tests
$ yarn run test:e2e