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, though FastAPI integration is entirely optional.

---

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(key) (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 and custom key_builder
• 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 sees a valid header, they won't even send the request to your FastAPI server
• 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
• Background expiry sweeper via FastAPI lifespan helpers
• Clean lifespan shutdown — background sweeper cancels without noisy tracebacks

---

What's New in v0.2.0

• Sliding TTL (sliding=True) — extends the lifespan of active cache entries on every successful read. Frequently accessed data (active sessions, hot config) stays warm; idle data still expires naturally.
• HTTP Cache-Control (http_cache=True) — offloads execution load entirely. If a client browser or a CDN sees a valid Cache-Control header with max-age, they won't even send the request to your FastAPI server — saving bandwidth and compute. Defaults to private; opt in to cache_visibility="public" for CDN-shared assets.
• ETag + 304 Not Modified (etag=True) — generates a stable content hash and handles If-None-Match conditional requests. When the client already has the current version, inhouse returns 304 Not Modified with an empty body instead of re-transmitting the full payload.
• remaining_ttl() store API — exposes seconds-until-expiry for a key; powers accurate max-age headers and enables future integrations.

Migration

No breaking API changes. All new parameters default to v0.1.x behavior:

• sliding=False
• http_cache=False
• etag=False
• cache_visibility="private"

---

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()
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=True → Cache-Control: max-age=N	The round trip entirely while fresh
3. Conditional HTTP cache	etag=True → If-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.

• 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

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).

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 (Worker) FastAPI prototype	Excellent	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

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 the Configuration Reference for full decorator and store options.

---

License

MIT