Tag: redis

  • Design Choices 1

    Today I looked more into how I will deal with communication between the indexer, database, and the API. First I thought if simply having an HTTP server that in itself is an a way a REST API, but this is terribly inefficient as it (at least in my design) does one operation per request. So…

  • ScratchDB: Project Update 1

    So for a decent part of today I looked into designing the leaderboard system. I researched various different ways to rank the data, going anywhere from a combination of HashMaps and BSTs to simply keeping my current solution of an oddly ranked array/Object combination in JS. At the end, the easiest and likely best solution…