Architecture Planning for Discord Service

[joyguptaa]

Issue Description

We do not have a central service that can handle global and route-specific API rate limiting for Discord API calls. As a result, we simply expect it to work, and sometimes we encounter internal server errors due to API rate limiting.

Expected Behavior

We should have a central Discord management service that takes care of every Discord-related task and manages API calls. It should also handle tasks based on their priority, allowing it to prioritize, deprioritize, pause, and resume tasks based on certain parameters. Additionally, it should automatically resume pending tasks upon revival or redeployment of the service.

Current Behavior

We simply expect all Discord-related API calls to work, as our system is not yet capable of handling Discord API calls globally

Expectations

1. By the completion of this task we expect to have a final architecture designed for discord service
2. Enough hands-on with Golang

Previous Design Docs

• https://docs.google.com/document/d/1Nv-qQ9pe_feX_ELkifmhsSKCSgM_uid0Sz95wBXZMHA/edit
• https://docs.google.com/document/d/14g6d-VAayT_li-Si5m8Ow2GL1t-pw9_tr7ygzAi05VA/edit#heading=h.alwnhbpscgoe

Reproducibility

• [x] This issue is reproducible
• [ ] This issue is not reproducible

Plan

Days	Task
7-10	Figuring out Architecture
7-10	Getting hands-on with Golang

Severity/Priority

• [x] Critical
• [ ] High
• [ ] Medium
• [ ] Low

Additional Information

This service is planned to be implemented in Golang.

Checklist

• [x] I have read and followed the project's code of conduct.
• [x] I have searched for similar issues before creating this one.
• [x] I have provided all the necessary information to understand and reproduce the issue.
• [x] I am willing to contribute to the resolution of this issue.