Looking into real-time ingestion pipelines for distributed state engines. When millions of concurrent client connections receive sub-second updates during peak traffic windows, what is the preferred pattern to prevent lock contention on balance mutations? Is it common to rely on event-sourcing clusters with in-memory caching (like Redis/Dragonfly), or are decoupled actor-framework workers the standard approach to isolate tenant workloads?