PitLane maps logical service identity to execution without requiring every workload to own an IP address or listener.
Stop wrestling with port ranges, NAT rules, and bridge networking. PitLane operates purely on logical ServiceIds.
ServiceId replaces application-visible machine addressing. Services are invoked as pit://service-name/path.
Multiple microservices share unified PitFast infrastructure networking without requiring individual TCP sockets.
PitFast services invoke each other through logical identities instead of per-service TCP listeners or sidecars.
Call services directly using the pit CLI without setting up DNS records or port forwarding.
# 1. Invoke a service via logical URI schema
pit call pit://service-a/hello
# 2. Pass headers and JSON payloads directly to logical endpoints
pit call pit://service-b/checkout -X POST -d '{"order_id": 49102}'
# 3. Stream responses from long-running component queries
pit call pit://service-c/events --streamEvery subsystem handles one distinct responsibility in the demand-driven execution chain.
Deploy multiple services on a single node without ever dealing with port allocation conflicts again.