ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine whether RocksDB removes TTL‑expired keys before applying a merge operator during compaction, and what impact this interaction has on write amplification and memtable usage. Constraints / Uncertainty The documentation states that TTL expiration is performed lazily during compaction or reads, but does not specify the order relative to merge‑oper
A design needs items to expire at a consistent local midnight in America/New_York and to remain sortable for range queries across daylight saving time transitions. DynamoDB provides no native datetime or timezone type. Temporal values are stored as String ISO 8601, Number epoch, or decomposed types. TTL evaluates a Number attribute as UTC Unix epoch seconds
Caching behavior of $http in AngularJS 1.8.2 When a small AngularJS application is migrated live, the $http service’s built‑in caching can return stale responses if the server data changes between requests. The cache is populated automatically when cache:true is set, but there is no built‑in timeout or invalidation policy. Unresolved Decision Point To avoid
An Azure Cosmos DB SQL (Core) API container previously had time-to-live enabled at the container level. Several items already contain expiration timestamp values, and some timestamps have passed while TTL was active. After disabling container-level TTL, it is unclear whether the asynchronous background cleanup continues to remove items whose expiration times
TTL Check Behavior In Consul, TTL checks require the service to send periodic heartbeats to keep the check in a passing state. If the heartbeat is not received within the TTL window, the check automatically transitions to critical . This mechanism shifts the monitoring responsibility from the Consul agent to the service itself. When many services register TT
The goal is to guarantee that the age of cached train‑position data never exceeds a distance‑based staleness limit derived from current speed, block length, and required reaction time, ensuring downstream signaling decisions rely on sufficiently fresh information. Presently the cache uses a fixed 30‑second TTL with no documented mechanism to vary this timeou
Redis 7.x key expiration unit boundary In Redis 7.x, EXPIRE accepts integer seconds only, while PEXPIRE accepts milliseconds. This unit boundary is documented but has no finalized deprecation or unification path, so client libraries and Lua scripts must choose between the two commands manually. The goal is to clarify whether applications migrating from earli
NestJS provides the CacheInterceptor to optimize response times by caching results based on a defined Time-To-Live (TTL). While this effectively reduces load for static or semi-static data, the default behavior triggers a cache miss immediately upon TTL expiration. In high-throughput environments, this creates a risk where multiple concurrent requests for th
Developers using Photon Realtime need to decide how to handle the room list cache that does not automatically expire entries based on time. The cache is refreshed only when the client calls OpGetRoomList or when the server pushes updates according to the lobby’s update interval, which can leave closed or full rooms visible longer than desired. The goal is to
dynamodb
cosmosdb
railway
redis
nestjs