Skip to content

Conversation

@alexmerren
Copy link
Owner

No description provided.

Before, we didn't split concerns well given we had an explicit
expiryTime to the cache interface. We invert the dependency here by
storing and returning the createdAt timestamp when records are added to
the cache.

We also had a tight coupling on always importing the sqlite cache, even
if you implement your own cache (i.e. redis, duckdb). Now, we split
implementations of the cache into their own module, which can be
imported if required.

Business logic to check if a request/result is okay to store/return has
been improved in transport.go as well.

Overall improvements, but have removed tests for easier redesigning.
Will (hopefully) add before the final release.
@alexmerren alexmerren closed this Dec 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants