Skip to main content

Zero-dependency, in-process TTL cache for Python. Optional FastAPI decorators, stampede-safe, LRU-bounded.

Project description

inhouse

Zero-dependency, in-process TTL cache for Python. One decorator, stampede-safe, LRU-bounded. For when Redis is a meeting you don't want to have, or when you need to avoid yet another deployment. Designed to be simple and effective without bloat or complexity for developers.

Keep hot data cheap to serve — v0.2.0 goes one layer deeper (memory → HTTP) with sensible defaults and no breaking changes.

Designed for easy use with FastAPI applications. Although FastAPI integration is absolutely optional.

Official Documentation/Release Notice:

Complete documentation by version is now managed by Rancero, and is available at https://docs.rancero.com/docs/category/inhouse-cache.

Install

The package is published on PyPI as inhouse-cache. Imports use inhouse (e.g. from inhouse import MemoryStore).

Core:

pip install inhouse-cache

With FastAPI helpers (fastapi_cache, lifespan sweeper):

pip install inhouse-cache[fastapi]

Quick start Usage

Core (any Python project)

from inhouse import MemoryStore, inhouse_cache

store = MemoryStore(max_size=1024, default_ttl=60)


@inhouse_cache(store=store)
async def load_user(user_id: int) -> dict[str, int]:
    return {"user_id": user_id}

Works with both async def and def callables.

FastAPI Use Case

import asyncio

from fastapi import FastAPI

from inhouse import MemoryStore
from inhouse.fastapi import create_lifespan, fastapi_cache

store = MemoryStore(max_size=1024, default_ttl=60)
app = FastAPI(lifespan=create_lifespan(store))


@app.get("/items/{item_id}")
@fastapi_cache(store=store)
async def get_item(item_id: int) -> dict[str, int]:
    await asyncio.sleep(0.1)  # expensive work
    return {"item_id": item_id}

Requires pip install inhouse-cache[fastapi].

FastAPI with HTTP caching (v0.2.0)

@app.get("/catalog/{item_id}")
@fastapi_cache(
    60,
    store=store,
    sliding=True,
    http_cache=True,
    etag=True,
    cache_visibility="public",
)
async def get_catalog_item(item_id: int) -> dict[str, int]:
    await asyncio.sleep(0.1)
    return {"item_id": item_id}

Features

Core (zero dependencies)

  • TTL cache with lazy expiry on read
  • Sliding TTL (v0.2.0) — opt-in touch-on-read extends active entry lifetimes; idle entries still expire
  • LRU eviction when max_size is exceeded
  • Per-key singleflight stampede guard - concurrent misses on the same key coalesce to one computation. Backend errors propagate to all waiters; client disconnect on the leader no longer aborts in-flight cache population for followers
  • Deterministic cache keys - canonical JSON serialization with type-qualified fallbacks for custom objects. Keyword argument order and Request subclasses don't cause spurious cache misses
  • Thread-safe store for sync and async callables
  • Fixed, store-default, or callable TTL on each cache write
  • Opt-in copy_on_read on MemoryStore — deep-copy cached values on read to prevent caller mutation from corrupting the cache
  • remaining_ttl() (v0.2.0) — introspect seconds-until-expiry for a cached key

Optional FastAPI extra (pip install inhouse-cache[fastapi])

  • @fastapi_cache with Request/Response-aware cache keys
  • HTTP Cache-Control (v0.2.0) — opt-in http_cache=True emits Cache-Control with max-age derived from remaining in-process TTL. Offloads execution load entirely: if a client browser or a CDN (like Cloudflare) sees a valid header, they won't even send the request to your FastAPI server — saving bandwidth and compute
  • ETag / 304 Not Modified (v0.2.0) — opt-in etag=True handles If-None-Match and returns 304 with an empty body when content is unchanged — a huge bandwidth win on repeat traffic
  • Background expiry sweeper via FastAPI lifespan helpers
  • Clean lifespan shutdown - background sweeper cancels without noisy tracebacks

Configuration reference

MemoryStore

from inhouse import MemoryStore

store = MemoryStore(max_size=1024, default_ttl=60, sliding=False)
Parameter / attribute Type Default Description
max_size int 1024 Maximum number of entries before LRU eviction
default_ttl float | None None Default TTL in seconds for store.set() and decorators that omit ttl_seconds
copy_on_read bool False When True, get() returns copy.deepcopy() of cached values so callers cannot mutate the store
sliding bool False Store-wide default for touch-on-read TTL extension on set()
sliding (property) bool Read-only; current store-wide sliding default
default_ttl (property) float | None Mutable at runtime; affects future writes only
size int (read-only) Current number of cached entries

Store methods:

Method Description
get(key, *, default=MISS) Return a cached value, or default on miss/expiry. Extends expiry on read when entry is sliding. Deep-copies when copy_on_read=True
set(key, value, ttl_seconds=None, *, sliding=None, etag=None) Write a value; uses default_ttl when ttl_seconds is omitted. sliding=None inherits store default
remaining_ttl(key) Seconds until expiry for a live entry, or None on miss/expired
entry_meta(key) (remaining_ttl, etag) tuple for a live entry, or None — single lock hop for HTTP header assembly
get_etag(key) Stored ETag for a live entry, or None
delete(key) Remove one entry
clear() Remove all entries
purge_expired() Proactively delete expired entries
keys() List current cache keys

@inhouse_cache / cache()

Core decorator. Works with both async def and def callables.

from inhouse import MemoryStore, inhouse_cache, make_cache_key

store = MemoryStore(default_ttl=60)

@inhouse_cache(
    ttl_seconds=60,          # optional — see Dynamic TTL below
    store=store,             # optional — defaults to a module-level store
    key_builder=make_cache_key,  # optional — custom cache key strategy
    exclude_types=(object,),     # optional — types omitted from key material
    sliding=False,           # optional — touch-on-read TTL extension
)
async def load_user(user_id: int) -> dict[str, int]:
    return {"user_id": user_id}
Parameter Type Default Description
ttl_seconds float | Callable[[], float] | None None TTL in seconds for each cache write. See Dynamic TTL.
store MemoryStore | None module default Cache instance to read/write
key_builder Callable[..., str] make_cache_key Builds the cache key from function identity + arguments. Non-JSON-serializable arguments fall back to module.qualname:str(value)
exclude_types tuple[type, ...] () Argument types excluded from key material (e.g. request objects)
sliding bool False When True, each successful read extends expiry by the entry's stored TTL duration

inhouse_cache is an alias for cache.

Global default store helpers:

from inhouse import configure_default_store, get_default_store

store = MemoryStore(default_ttl=120)
configure_default_store(store)

@inhouse_cache()  # uses the configured default store + its default_ttl
async def load_config() -> dict[str, str]:
    ...

Sliding TTL

Fixed TTL expires on an absolute deadline set at write time. Sliding TTL extends that deadline on every successful read by the entry's stored TTL duration — so frequently accessed data stays warm while idle data still expires naturally.

@inhouse_cache(60, store=store, sliding=True)
async def load_active_session(session_id: str) -> dict[str, str]:
    ...

Why use it: active user sessions, hot configuration, or any data accessed repeatedly within a window should stay cached without arbitrary mid-activity expiry.

Caveat: a continuously read key can live indefinitely until LRU eviction at max_size. Callable TTL is still evaluated on write only; sliding reuses the duration stored at the last write.

@fastapi_cache (optional — requires inhouse-cache[fastapi])

FastAPI-friendly wrapper around inhouse_cache. Automatically excludes Starlette Request and Response objects from cache keys.

from inhouse.fastapi import create_lifespan, fastapi_cache

store = MemoryStore(max_size=512, default_ttl=60)
app = FastAPI(lifespan=create_lifespan(store, sweep_interval=30.0))

@app.get("/items/{item_id}")
@fastapi_cache(store=store)
async def get_item(item_id: int) -> dict[str, int]:
    ...
Parameter Type Default Description
ttl_seconds float | Callable[[], float] | None None Same semantics as @inhouse_cache
store MemoryStore | None module default Cache instance to read/write
key_builder Callable[..., str] | None make_fastapi_cache_key Custom key builder. Defaults exclude Starlette Request/Response; override delegates that responsibility to you
sliding bool False Touch-on-read TTL extension (same as @inhouse_cache)
http_cache bool False Emit Cache-Control with max-age from remaining in-process TTL
cache_visibility "private" | "public" "private" Cache-Control visibility. Use "public" only for CDN/browser-shared assets
etag bool False Generate stable ETag and handle If-None-Match / 304 Not Modified

Custom key_builder functions replace the FastAPI-aware default. To keep Request/Response exclusion, delegate to make_fastapi_cache_key or pass your own exclude_types.

When http_cache=False and etag=False, behavior is identical to v0.1.x (returns plain Python objects, no HTTP headers).

FastAPI-injected request is used only to read If-None-Match; it is stripped before your route handler runs and excluded from cache keys via make_fastapi_cache_key.

HTTP caching (FastAPI)

v0.1.x optimized the server (in-process TTL, stampede guard, LRU). v0.2.0 adds an optional HTTP layer so repeat clients may never hit your app at all when freshness allows.

Three complementary layers:

Layer Mechanism What it saves
1. In-process cache @fastapi_cache / MemoryStore Server compute on repeat hits
2. Time-based HTTP cache http_cache=TrueCache-Control: max-age=N The round trip entirely while fresh
3. Conditional HTTP cache etag=TrueIf-None-Match / 304 The response payload when the round trip happens anyway

HTTP Cache-Control (http_cache=True)

Offloads execution load entirely. If a client browser or a CDN (like Cloudflare) sees a valid Cache-Control: public, max-age=30 header, they won't even send the request to your FastAPI server — saving bandwidth and compute.

  • max-age is derived from store.remaining_ttl(key) on cache hits, so HTTP freshness tracks in-process TTL (including sliding extensions)
  • Defaults to Cache-Control: private, max-age=N — safe for user-specific responses
  • Opt in to cache_visibility="public" for CDN-shared public assets

ETag / 304 Not Modified (etag=True)

When a client already has the current version, inhouse returns 304 Not Modified with an empty body instead of re-serializing and re-transmitting the full response — a huge bandwidth win on repeat requests.

  • Stable weak ETag (W/"<sha256>") computed at cache-write time via canonical JSON digest
  • If-None-Match handled on cache hits and misses (recompute + matching ETag still skips body transfer)
  • Pairs naturally with Cache-Control: the browser/CDN may skip the request entirely; if a conditional request arrives after expiry, 304 skips the payload
sequenceDiagram
    participant Client as Browser_or_CDN
    participant FastAPI as fastapi_cache
    participant Store as MemoryStore

    Client->>FastAPI: GET with optional If-None-Match
    FastAPI->>Store: get(key)
    alt cache HIT
        Store-->>FastAPI: value + remaining_ttl
        alt ETag matches
            FastAPI-->>Client: 304 Not Modified empty body
        else full response
            FastAPI-->>Client: 200 + Cache-Control + ETag + body
        end
    else cache MISS
        FastAPI->>FastAPI: run handler via singleflight
        FastAPI->>Store: set(key, value, etag)
        alt ETag matches If-None-Match
            FastAPI-->>Client: 304 Not Modified empty body
        else
            FastAPI-->>Client: 200 + Cache-Control + ETag + body
        end
    end

Return types: HTTP caching modes return Starlette JSONResponse or 304 Response. Best suited to JSON-serializable dict/list/Pydantic returns. Routes returning custom Response subclasses should omit http_cache / etag.

Lifespan / background cleanup (optional — requires inhouse-cache[fastapi])

from inhouse.fastapi import create_lifespan, inhouse_lifespan

# Option A: pass directly to FastAPI
app = FastAPI(lifespan=create_lifespan(store, sweep_interval=30.0))

# Option B: use inside your own lifespan
async with inhouse_lifespan(store, sweep_interval=30.0):
    ...
Parameter Type Default Description
store MemoryStore required Store to sweep for expired entries
sweep_interval float 30.0 Seconds between background purge runs

Dynamic TTL

TTL is resolved when a value is written to the cache (on a miss), not on every read. Changing TTL settings does not retroactively extend entries already stored.

With sliding TTL, successful reads extend expiry by the TTL duration stored at the last write (not by re-evaluating a callable TTL).

Three ways to configure expiration:

1. Fixed TTL (per route)

@inhouse_cache(60, store=store)
async def load_user(user_id: int) -> dict[str, int]:
    ...

Always expires 60 seconds after the value is cached (unless sliding=True extends it on read).

2. Store default (mutable at runtime)

store = MemoryStore(default_ttl=60)

@inhouse_cache(store=store)
async def load_config() -> dict[str, str]:
    ...

# Later - affects future cache writes only
store.default_ttl = 300

Omitting ttl_seconds on the decorator uses store.default_ttl. If both are missing, inhouse raises ValueError.

store.default_ttl is safe to change at runtime from other threads; new writes pick up the updated value atomically.

3. Callable TTL (evaluated on each write)

settings = {"cache_ttl": 60}

@inhouse_cache(lambda: settings["cache_ttl"], store=store)
async def load_dashboard() -> dict[str, str]:
    ...

settings["cache_ttl"] = 300  # next cache miss uses 300 seconds

Useful for feature flags, config files, or environment-driven TTL without redeploying.

Priority order

When a cache miss is written, TTL is resolved as:

  1. Callable ttl_seconds() result, if a callable was passed
  2. Fixed ttl_seconds float, if provided
  3. store.default_ttl, if set
  4. Otherwise → ValueError

When to use inhouse

Scenario inhouse Redis fastapi-cache2
Single-node FastAPI prototype Great Overkill Great
Zero external infrastructure Yes No Depends on backend
Distributed multi-instance cache No Yes Yes (with Redis)
Decorator-first developer UX Yes No Yes
Browser/CDN HTTP caching (v0.2.0) Yes (opt-in) No Depends on backend

Important limitations

inhouse is per-process memory. If you run uvicorn main:app --workers 4, each worker maintains its own independent cache. That keeps the design simple and avoids shared infrastructure. It is not a distributed cache.

HTTP cache independence (v0.2.0): in-process TTL and HTTP Cache-Control / ETag freshness are related but not identical. Calling store.delete() or waiting for in-process expiry does not invalidate browser or CDN copies. Plan HTTP cache durations and invalidation accordingly.

Architecture

flowchart TB
    subgraph fastapi_layer [Optional FastAPI Integration - inhouse.fastapi]
        FDecorator["fastapi/decorator.py: @fastapi_cache"]
        HttpCache["Cache-Control + ETag/304 via _respond"]
        ReqStrip["Strip Request before handler"]
        FLifespan["fastapi/lifespan.py: create_lifespan"]
        FKeys["fastapi/keys.py: excludes Request/Response from keys"]
    end

    subgraph core [Zero-Dependency Core]
        Entry["entry.py: CacheEntry ttl_seconds sliding etag"]
        KeyBuilder["keys.py: make_cache_key + make_weak_etag"]
        Store["store.py: MemoryStore entry_meta remaining_ttl"]
        Singleflight["singleflight.py"]
        Sweeper["sweeper.py: ExpirySweeper"]
    end

    FDecorator --> FKeys
    FDecorator --> ReqStrip
    FDecorator --> HttpCache
    FKeys --> KeyBuilder
    HttpCache -->|"entry_meta: max-age + etag"| Store
    FDecorator --> Store
    FDecorator --> Singleflight
    FLifespan --> Sweeper
    Sweeper --> Store
    Store --> Entry
    Store -->|"OrderedDict + sliding touch-on-read"| Memory[(In-Process Memory)]

Core API

The core package has no runtime dependencies. Import from inhouse directly:

from inhouse import MemoryStore, configure_default_store, inhouse_cache, make_cache_key

See Configuration reference for full decorator and store options.

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

inhouse_cache-0.2.0.tar.gz (15.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

inhouse_cache-0.2.0-py3-none-any.whl (17.7 kB view details)

Uploaded Python 3

File details

Details for the file inhouse_cache-0.2.0.tar.gz.

File metadata

  • Download URL: inhouse_cache-0.2.0.tar.gz
  • Upload date:
  • Size: 15.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for inhouse_cache-0.2.0.tar.gz
Algorithm Hash digest
SHA256 515148720d2438b57b99df6820d8cdff5181c31bcb7768afbba5dcfbb3f7fcee
MD5 2bfabc2a097a7abed9cdc73e28c223f6
BLAKE2b-256 30cd34f098f55de71ead198669a72470119ffdb59f482ff88bc0950ed624b7a7

See more details on using hashes here.

Provenance

The following attestation bundles were made for inhouse_cache-0.2.0.tar.gz:

Publisher: publish.yml on kineticquant/inhouse

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file inhouse_cache-0.2.0-py3-none-any.whl.

File metadata

  • Download URL: inhouse_cache-0.2.0-py3-none-any.whl
  • Upload date:
  • Size: 17.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for inhouse_cache-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 b8a52837744dc4326272d35afdc432b1dfbd7a155f73b6c2a6de7a85fd5aaef3
MD5 6592a1916041614145f7f581c1b4faa3
BLAKE2b-256 f1f7e848403d921928b29ed4c4cad08c825df5bde3353c55499bc6e22ae7eaea

See more details on using hashes here.

Provenance

The following attestation bundles were made for inhouse_cache-0.2.0-py3-none-any.whl:

Publisher: publish.yml on kineticquant/inhouse

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page