Deploy like microservices. Perform like a monolith. Evolve like a living organism. A Kubernetes-native runtime for zero-copy function composition.
Deploy 4 functions. Watch them share memory. Process a request in microseconds.
Every platform before KubeFn forces you to pick two. KubeFn gives you all three.
✓ Shared memory ✗ Independent deploy ✗ Hot-swap
✗ Shared memory ✓ Independent deploy ✗ Hot-swap
✗ Shared memory ✓ Independent deploy ✗ Hot-swap
✓ Shared memory ✓ Independent deploy ✓ Hot-swap
Zero-copy shared object graph between functions. No serialization. No network. Same memory address. Function A's output IS Function B's input.
New function revisions enter an already-hot JVM. Shared libraries are JIT-compiled. Peak performance in <1 second, not 30+ seconds.
Replace individual functions while traffic flows. Zero dropped requests. The organism lives — only the organ is replaced. Tested: 200/200 successful.
Compose functions into in-memory execution graphs. The runtime owns the graph, traces it, and can optimize it. 7 steps in 0.458ms.
Per-function failure isolation. If one function fails, the breaker trips — protecting the shared organism from cascade failures.
OpenTelemetry spans per function with revision IDs, request lineage, and heap mutation tracking. See exactly what happened in memory.
Functions are independently deployable but collaborate through shared heap objects.
// Zero-copy: publish once, read everywhere @FnRoute(path = "/pricing") @FnGroup("checkout") public class PricingFunction implements KubeFnHandler { public KubeFnResponse handle(KubeFnRequest req) { // Read from HeapExchange — SAME object, zero copy var auth = ctx.heap().get("auth", Map.class); var price = Map.of("total", 84.99); ctx.heap().publish("price", price, Map.class); return KubeFnResponse.ok(price); } }
Replace a function while 200 requests are in flight. Zero downtime.