ZLink approach — web service + real-time

Server-to-server goes direct over channel · the overhead collapses to one location store

ZLink approach — web service + real-time Server-to-server goes direct over channel · the overhead collapses to one location store Client app · Architecture component Client app L7 LB / gateway · HTTP unchanged · Architecture component L7 LB / gateway HTTP unchanged API servers ×N · API + ZLink · route client · Architecture component API servers ×N API + ZLink · route client Domain ×N · SPOT(order/conv) · STREAM · Architecture component Domain ×N SPOT(order/conv) · STREAM location store · descriptor rows · Architecture component location store descriptor rows HTTP channel (direct) STREAM address resolution registration

Server-to-server over channel (the core)

  • • API servers ↔ Domain servers: channel request/send goes direct (no broker, no sticky LB)
  • • Client connects directly to a Domain server over STREAM (direct STREAM connect)
  • • Domain server = the SPOT owner for one order/conversation (serial, no distributed lock) + STREAM host
  • • Both are ASP.NET Core + ZLink; the API server routes the client

location store = discovery only

  • • Holds descriptor rows — address resolution (API) and registration (Domain) only, not a data/message path
  • • That's why its links are dotted (control plane)