Platform Components

Roomzin

Core engine

Stores the hot booking window in memory using a schema designed for travel inventory. Organized into shards with replication for high availability. Optimized for filtering by location, dates, room type, availability, price, amenities, and policies.

RzBridge

Shard-aware connector

Connects the routing layer to a Roomzin shard. Knows which Roomzin nodes belong to the shard and which node is currently the leader. Routes writes to the leader and reads to followers. Isolates shard topology from routers.

RzRouter

Routing fabric — single binary, two modes

RzProxy

HTTP/JSON proxy

Lightweight proxy that accepts HTTP/JSON requests and translates them to Roomzin's internal protocol. Deploy independently, scale horizontally. Perfect for legacy platforms, testing, or third-party integration.

SDKs

Native clients

SDKs connect directly to Edge Routers. They handle serializationand connection pooling — no need to discover shards, zones, or bridges.

RzID

Control-plane registry

Lightweight service registry. Components register their identities and send heartbeats. Maintains topology — which shard owns which segments. Routers fetch updated routing information when topology changes.

RzPoint

Service identity → hostname resolution

Not provided by Roomzin. A small HTTP service that you implement based on your infrastructure. Translates logical service identities (e.g., bridge-europe-03) to hostnames (bridge-europe-03.internal.company).