AsyncCacheRegion

Open
#199 15 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
memcached, python, redis
Domain
backend, databases

Research direction

Start by reading SQLAlchemy's referenced lib/sqlalchemy/util/_concurrency_py3k.py and then inspect dogpile.cache's region and backend interfaces. Define the AsyncCacheRegion frontend and its sync greenlet adaptation, beginning with aiomcache and aioredis; done means both listed async backends work through the new frontend.

Written by the indexing model from the issue text.

Description

asyncio feature

adapt the approach taken by SQLAlchemy in https://github.com/sqlalchemy/sqlalchemy/blob/master/lib/sqlalchemy/util/_concurrency_py3k.py to provide for an AsyncCacheRegion frontend.

backends will as always present a "sync" interface that uses greenlets to adapt to the async backend. backends to start with:

Dominant language
Python
Stars
299
Forks
50
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sqlalchemy/dogpile.cache

All issues in sqlalchemy/dogpile.cache

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.