07/31/2026
By the time Hamieverse reached Beta, its database had already changed shape twice. No player ever noticed.
Pre-Alpha read straight from the database, no caching. Right call for a handful of testers — speed was everything.
As the player base grew, Alpha introduced a hot/cold table split: live match data on a narrow, high-speed table, older matches archived where they’re rarely queried.
This wasn’t a stopgap. It was a deliberate optimization that kept gameplay smooth enough to safely add longer matches and more cards.
Beta went further: Redis in front of reads for menus, store, and leaderboards. Read/write replicas keep the primary database lag-free during live matches.
None of these swaps touched the layers above them. Prisma acts as a secure pipeline — not a query generator — triggering stored procedures behind a stable interface.
The storage strategy changes underneath. The callers never do. Next in this series: the leaderboard system we only had to build once.
About Hamieverse:
▪️ Hamieverse is a competitive, turn-based card combat game with a rapidly growing community.
▪️ Built in Unity for WebGL, playable directly in a browser.
▪️ The engineering, architecture, backend, and everything that lets it scale is built by Algoryte.
