Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offload processing of data away from the endpoints. #67

Open
RealistikDash opened this issue Mar 23, 2024 · 0 comments
Open

Offload processing of data away from the endpoints. #67

RealistikDash opened this issue Mar 23, 2024 · 0 comments

Comments

@RealistikDash
Copy link
Member

Currently, all of the processing for user data is done during handling the endpoint. This is bad from a scaling standpoint. Ideally, the bare minimum should be done during the request itself (such as just a simple DB insert).

This should be off-loaded to processors running ideally on a separate process. These will be distributed over AMQP and handled. Likely will require an additional field per model dedicated to keeping track of whether these have already been processed and can be displayed to other users.

Some of the places I can see this being implemented are:

Levels:

  • Meili indexing
  • Level content analysis

Users:

  • Meili indexing
  • Stats anticheat
  • Stats analysis

Messages:

  • Spam filter

User comments:

  • Spam filter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant