Use some sort of queue to spin up tasks, or lambdas
Actions that may need this

• Getting demo data, parsing and putting into db
• Analyzing demos at bulk and importing bomb attempts into db

Use redis or dynamodb or something

Create a cron job for importing the logs automatically, and store the cache files somewhere. Right now I am thinking of a table in dynamodb which contains all the rosters, etc (just because it is free and can act as a k-v store) although I'm not sure how feasible this is with filesize and whatnot. I can also just store everything in the github repo itself so it is version controlled.

Split into each phase (accquisition/getting data, analysis, etc)
I realize now that they do not share a lot of the same logic, so it makes sense they are their own modules instead of lumped together in one file.

Also this makes it easier to tell apart the binaries from the other functions
And put the API code/lambda functions in another place.

Have this be on a per-map basis

The SteamID64s being returned by the lambda function is incorrect. I have a feeling that this is because I changed from my own steamid parser to the steamid-ng crate

It should not take 10-15 seconds per demo, that is insane. I think the biggest bottleneck are the props at the moment. Will look into optimizations

Everything is getting so complex especially with all the rewriting and refactoring as of late.. need to write some tests.

Create landing page for svelte code so that the logic can be put into separate folders for routes. Right now everything is inside one file and this is very messy.