Feature/ext cache/core and caffeine #14
Assignees
Relism (Zakaria El Orche)
Clear assignees
Relism (Zakaria El Orche)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Relism/Flash5#14
Reference in New Issue
Block a user
Boots a real app on an OS-assigned port for a test class or a single test and hands back a client pointed at it: @RegisterExtension static FlashTest app = FlashTest.of(new BlogApp()) .mock(UserService.class, new InMemoryUserService()); app.get("/api/users").expectStatus(200).expectBodyContains("alice"); A field rather than an annotation, because annotation values are compile-time constants and so could never express a second server wired from the first — FlashTest.of(new BlogApp(auth.baseUri())). Startup is lazy, so reading baseUri() boots that server on the spot and declaration order does the wiring, with no dependence on JUnit's extension ordering. A static field boots once per class, a non-static field once per test; that is stock JUnit field semantics rather than an option to configure. Runs against a real loopback port instead of dispatching in-process. An in-process dispatcher would be a third copy of the routing/handler/exception sequence that Http1Connection and Http2StreamDispatcher already duplicate, kept in sync by hand, and it would let a test pass while the status line, content-length or HPACK encoding was broken. mock() installs overrides as the last extension, after everything the application and its extensions declare, so a fake always wins. Any object is accepted, so a hand-written fake and a Mockito mock are equally welcome and this module depends on no mocking library — only flash and junit-jupiter-api. Teardown cancels the client before stopping the server: HttpClient holds keep-alive sockets open and ServerLifecycle.stop() spins until the last one closes, so the default 15s drain would otherwise be paid on every test class. shutdownNow rather than close(), which blocks until every operation completes and would hang on a leaked WebSocket. Lives at the top level, not under flash-extensions/, which holds things you install() onto an app; this carries junit-jupiter-api at compile scope and nothing installable should. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>Split the way flash-ext-data and flash-ext-view are: cache-core defines Cache, CacheManager, CacheSpec and CacheStats and talks to nothing; cache-caffeine implements them in process. users = require(CacheManager.class).build("users", spec -> spec .maxSize(10_000).ttl(Duration.ofMinutes(10))); return users.get(id, repo::findById); get(key, loader) is the only shape most code needs and the only one that is hard to get right: the loader runs once per key across concurrent callers rather than each racing its own. A null result stores nothing, because caching absence is a decision rather than a default. build(name, spec) is idempotent per name, so two handlers wanting one cache get one cache without coordinating who creates it. Disagreeing about the spec throws rather than resolving to whichever handler initialised first, which is a bug that only surfaces under load. recordStats() is opt-in — counting is two atomic increments per lookup, and a cache nobody measures should not pay for numbers nobody reads. Unmeasured caches return CacheStats.DISABLED rather than zeroes that look like a cold cache. Caffeine rather than a hand-rolled LRU: for genuinely low traffic ConcurrentHashMap::computeIfAbsent is one line and needs no module at all, and this exists for when that stops being true. W-TinyLFU admission, striped counters and amortised eviction are not a weekend's work, and getting them wrong yields a cache slower than no cache. The adapter is deliberately thin — every method delegates, adding no wrapper, copy or locking of its own. Caches are dropped through FlashContext.onClose, so values do not outlive the app holding them. Invisible with one app per process; immediate under test. flash-ext-cache-redis is designed but not built, and has docs only — no module, no pom, no source. An empty module that builds an empty jar is dead weight in the reactor. The docs record what changes once the cache can fail: get() must decide whether to fall through to the loader, values need a codec, invalidateAll needs a key prefix that becomes wire contract, and eviction stats stop meaning anything. Those are decisions that want a real second replica to check them against. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>