BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-165@sf26-agenda
DTSTAMP:20261020T151709Z
DTSTART:20261105T001500Z
DTEND:20261105T010000Z
SUMMARY:These are not the brokers you are connecting to
LOCATION:Room 2008
DESCRIPTION:Sam Barker\n\nEvery platform team has dreamt of splitting an Ap
 ache Kafka cluster\, but the reality is far messier. Application teams thi
 nk in topics and clusters\, but Kafka forces them to care about broker top
 ology. We can't fix that\, but this talk is about giving platform teams th
 e tools required to make that dream come true. Most proxies operate on Kaf
 ka at Layer 4 — they forward connections\, not messages. Kroxylicious wo
 rks at Layer 7: it understands individual Kafka protocol messages and cont
 rols the broker topology the client sees. Multiple physical clusters can a
 ppear as one\, or one cluster can appear as many — the client's view is 
 whatever the platform team decides it should be. The foundation for this i
 s Kroxylicious's new routing API — a plugin interface that lets you buil
 d custom routing logic as first-class extensions. Router authors decide wh
 ere messages go; the proxy handles making the broker topology look coheren
 t to the client. This enables a family of patterns: Union Clusters — top
 ics from multiple physical clusters presented as one; Union Topics — a s
 ingle topic sharded across clusters; and Cluster Aliasing — presenting o
 ne cluster under the identity of another. It also lets the proxy transpare
 ntly leverage KIP-392 for AZ-aware fetching. This talk will show you how t
 he routing API works\, walk through the patterns routers enable\, and give
  you everything you need to build a router. All you need to bring is your 
 own use case.
URL:https://sf26.rmoff.net/s/these-are-not-the-brokers-you-are-connecting-t
 o-165
END:VEVENT
END:VCALENDAR