Skip to content
This repository has been archived by the owner on May 16, 2019. It is now read-only.

High latency databases, caching, multiple databases support #112

Open
stackdumper opened this issue Mar 22, 2019 · 0 comments
Open

High latency databases, caching, multiple databases support #112

stackdumper opened this issue Mar 22, 2019 · 0 comments
Assignees

Comments

@stackdumper
Copy link
Member

stackdumper commented Mar 22, 2019

The problem lays in the requirement of low latency reads along with strong distributed persistency.
TBD.

Thoughts
  • Caching might be implemented as a plugin that memoizes N last reads (in memory or in database like Redis)

Multiple databases

Following approach will significantly improve read speeds for the cost of slower writes and first reads (cold start). Also, not found requests would become slower, can be sped up by explicitly setting package as nonexistent for the Fast database.

Overview

Workflow

First request - not cached

Second request - cached

@stackdumper stackdumper self-assigned this Mar 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant