Early Backend Decisions That Become Technical Debt Before You Know It

You are six months into building a multiplayer game with a team of five. The backend is whatever got the prototype playable: a player account table you wrote in a weekend, save data serialized to JSON in a bucket, a host-migration scheme that mostly works, and matchmaking that pairs the next two people in the queue. It runs.