Investigate AWS integration

[DP94]

If we move the code to the cloud then it can scale & be maintained much easier.

We should look at:

• Database storage (likely DDB)
• Lambdas for processing
• SQS events

[samkio]

My thinking on this: This is not directly the AWS integration investigation but it is somewhat related. Nothing we have implemented so far needs to be Minecraft specific (or Minecraft onDeath specific). A lot of it can be made generic such that it is a way to integrate anything with an API to check for a donation. This could be for any game (or any web-app). This would mean that the usecase of this could expand and have further impact by being able to collect donations in multiple different scenarios.

If we keep this in mind when looking at the architecture for AWS integration then we can separate what is generic (the interaction with JG and having a database of what "tokens" have donated and how much); and having a tenanted FE for donation pages. The Minecraft implementation is then just one use case of this (and anything specific to that usecase should remain in the plugin; i.e. death counts, leaderboard etc).

Happy to discuss this further but wanted to write it down and have a diagram before I forgot. 😆

[samkio]

Ideas

https://aws.amazon.com/amplify/

[VTVDV]

I really like the idea of making it game agnostic! :) The bulk of the just giving logic would be the same if we remade it for different games so it makes sense to try and separate it out.

[DP94]

Great diagrams, Sam. Love the idea of game agnosticism too. Love the league idea but riot fiercely defend their servers and have no public API to interact with 😆