Bee-Queue VS system-design-primer

You could use a Redis based job system like https://github.com/bee-queue/bee-queue for maintenance and email. The jobs could be populated by the API service, some cron scripts, and whatever else, while you'd have dedicated worker processes (written in Node.js?) pulling the jobs and running them.

The Node.js libraries BullMQ and Bee Queue are also infrastructure and interface. However, you typically have to use their interface.

I'm a fan of bee-queue for this when working in Node, but it's just a wrapper around reliable queue patterns in Redis; you might want to investigate how it works (the readme is quite good) for your own use case, or find an equivalent for your environment. The key is it's designed for short tasks (seconds long, not minutes or hours), and you can receive a result back from the task unlike some fire-and-forget queueing solutions.

I'd also consider something like bee-queue, which would enable you to scale across processes or even across multiple server machines.

For NodeJS, there are BullMQ(successor of Bull), Bull and Bee Queue

bee-queue for offloading tasks onto non-web-server machines

✅ donnemartin/system-design-primer: https://github.com/donnemartin/system-design-primer

View on GitHub

I've been giving interviews for past couple of months and this github repo has helped me so much for system design perspective and I can see myself excelling at interviews. - https://github.com/donnemartin/system-design-primer

You'll be on opiod's probably the first 1-2 days, so sleeping should be fine. Everything will be allright, don't worry too much. Just use the time now to prepare for the time after, make sure you go through post-surgery-essentials thread. Once you are out of the OR you won't have the energy to think about those details, so make sure you take that prep serious.

Tooling isn’t architecture. Figure out what you need to handle both personas and volume/throughput and then lay out the capabilities you’ll need. As you lay out points of ingress, egress, consumption you can start to lay out sequences(think in persona and sequence diagrams to express interactions between services). Lastly, evaluate tools that offer some of these capabilities and weigh the trade-offs (there are always trade-offs: https://github.com/donnemartin/system-design-primer).

[1] https://github.com/donnemartin/system-design-primer [2] https://www.teamblind.com/post/My-Approach-to-System-Design-V4SJARdx