[r00fus]

Couldn't you cache the reads? Not many usages really require real-time from their data store.

[RockRobotRock]

Do you really want to deal with caching logic for what should be a simple API call? Sounds like a convincing argument to use whatever this product is.

[kellpossible2]

It's max a couple of hours work to cache in some local database like sqlite or in memory.

[internetter]

client = (APIcall) => redis.get(sha1(APIcall)) || { res = api(APIcall); redis.set(sha1(APIcall),res) return res }

Not that hard. Like 10 lines of code to get a decentish cache going.

[hot_gril]

Assuming you have Redis

[internetter]

Redis uses like 5mb of baseline RAM and can be deployed in a few lines of docker-compose.

[hot_gril]

I'm not allowed to do that where I work. License is a no-no, can't run jobs without red tape, and there's no Docker either.

[internetter]

Ok? I'm surprised your work lets you build a whole product ontop of google sheets, then. Also, why did you delete your original comment on not having a server?

[randomdata]

Hell, just stick the data in memory.

[hot_gril]

Valid strategy