We study a practical hybrid front door for message oriented systems: REST (HTTP/1.1 keep-alive) and WebSocket,
backed by transformer-inspired queues. We compare synchronous FlashQueue against asynchronous FlashQueue (k-way
servers) and a MemoryMappedFlashQueue with hot/cold buffers.
Metrics: mean/p95 latency, throughput, CPU-cost proxy, connection amortization, and cache-hit ratio. Results show that (i)
persistent WebSocket amortizes connection setup and reduces
per-message overhead, (ii) async FlashQueue improves utilization
under load, and (iii) MemoryMappedFlashQueue wins on hitheavy workloads.