Skip to content

ZLink Framework Kotlin — User Guide

The order to use ZLink Framework in a Kotlin/Spring Boot environment. Chapters 03–17 share the same source across every language, and the example switches to Kotlin code when you pick the .kt tab.

Order Document Content
1 1. Overview What the Kotlin layer adds, the four integration axes, and the overall topology
2 2. Getting Started Dependencies, registration, the suspend handler, two ways to call
3 3. Core Concepts Channel · Spot · Actor · session · relocation
4 4. Backpressure How the system behaves when arrival outpaces processing, and the options that affect it
5 5. Channel Messaging Registering and calling request / send / pub-sub
6 6. Spot A dynamic state unit such as a room · stage · zone
7 7. Actor And Spot Actor hosting, membership, relocation
8 8. Session And Actor Binding Session ↔ Actor relay · binding · push
9 9. STREAM External-client real-time connections and the Stream Connector
10 10. Location Registering a location store, auto-connect, operational queries
11 11. Monitoring Receiving with a Flow, lambda observers
12 12. Operations Runtime metrics, graceful drain, readiness
13 13. Key Type Usage Index The suspend contract, the .kotlin() wrapper, extension functions
14 14. Picking A Sample How to choose which sample to look at first and run it
15 15. E2E Testing How to verify the whole system with the client
16 16. Options The option surface is the same as Java's
17 17. Where ZLink Fits Where it's used, the warning signs, and the boundary of the technology choice

The file number identifies the same chapter regardless of language. This table owns the reading order.

Kotlin runs on the Java runtime as-is. zlink-framework-kotlin isn't a separate implementation — it's a thin layer that adds coroutine idioms. So this guide writes up only what differs from Java and points everything else at the Java guide.

  • 01, 02 — the dependency and registration code differs, so these are Kotlin-specific.
  • 11, 13, 16 — the surface matches Java; only the idiom differs. This guide writes up only the difference and points the rest at the Java chapter.

The goal is not to keep two copies of the same content. When the Java document changes, Kotlin readers see the same document.