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

High latency databases, caching, multiple databases support #112

@stackdumper

Description

@stackdumper

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions