Workers KV for Session State: An Architecture Note
Workers KV removes the origin round trip from session lookups, but its consistency model decides your logout behavior, your cache settings, and when you need Durable Objects instead.
Loading…
ReadMeFeed / Community knowledge
#session-management
Real questions. Useful conversations. Find the people who know your stack.
cloudflareLet MongoDB Delete Your Expired Data: TTL Indexes as an Engineering Decision
MongoDB TTL indexes delete expired sessions, tokens, and logs for you — no cron job required. Here's how they work, where they fall short, and how to verify them.
mongodbPassport.js Local Strategy: Why serializeUser and deserializeUser Matter for Session State
Learn how Passport.js splits user data between the session cookie and your data store, and how to tune this trade‑off for scalability and security.
nodejsPassport.js Local Strategy with Server-Side Sessions: An Architecture Note
Architecture note on the minimal Passport.js design for first-party login: passport-local strategy with express-session backed by Redis, covering trust boundaries, operational checks, failure modes, and when to switch to token-based auth.
Choosing Session Storage in Ory Kratos: Cookie vs Token for Web Apps
Decide whether to use cookie‑based or token‑based sessions in Ory Kratos. Compare security, cross‑domain support, and implementation steps in a compact decision table, then walk through a concrete config and validation.
oryTTL Indexes in MongoDB: Automate Session Cleanup Without Cron Jobs
Learn how MongoDB TTL indexes can automatically purge stale sessions, the background expiry thread, and the trade‑offs versus manual jobs.
Scaling Yii2 Session and Query State with Redis
Learn how to scale Yii2 applications by migrating sessions and query caching to Redis, eliminating sticky sessions and reducing database load.
redis
yiiNHibernate FlushMode.Auto Produces Divergent Auto-Flush Decisions Across Query APIs
NHibernate's automatic flush behavior under FlushMode.Auto is documented as a heuristic that flushes pending changes before a query only when the session determines the query might touch the same entity or table spaces. In workflows that mix HQL, Criteria, QueryOver, and LINQ against the same transaction, developers face an unresolved consistency decision: w
nhibernateGatling HTTP‑JMS Session Scope Interoperability: Can Shared Session Attributes Cross Protocol Boundaries?
The objective is to verify whether a session attribute created by an HTTP request remains accessible when a subsequent JMS request is executed within the same Gatling scenario. Constraints include using only built‑in session handling, testing on Gatling 3.7 and 3.8 to capture the documented change in session scope, and avoiding external feeders or databases.
gatling