Decide if JSON is futureproof enough #6
Description
Currently all of our benchmark results are written to JSON files, which we then fetch from GitHub to display.
This is a simple solution, but has some downsides in terms of futureproofing - there's no way to introduce pagination should it become necessary, for example.
Our data structure also involves some duplication (library names and versions) which would increase the JSON size.
Using a full database (for example, using Supabase) would be a large step up in complexity, but would give us the ability to introduce such features and deduplication.