One host for every component.
teleon.dev/docs/topology keeps the one-host map: every component has a page at teleon.dev/docs/<name> and an API path at api.teleon.dev/v1/<name>, one to one. A signed rendezvous ring spreads load, and a five-tier cache keeps answers flowing when a backend slows.
| Page | API path | Tier |
|---|---|---|
| teleon.dev/docs/cas | api.teleon.dev/v1/cas | Edge cache |
| teleon.dev/docs/search | api.teleon.dev/v1/search | Edge cache |
| teleon.dev/docs/queues | api.teleon.dev/v1/queues | Origin |
| teleon.dev/docs/files | api.teleon.dev/v1/files | Edge cache |
One host for people and agents: pages at teleon.dev/docs, calls at api.teleon.dev.
What it does
One map for pages and calls
Each component's page and API path come from one map, so links and calls stay in step.
Balanced by two choices
Each request picks the less loaded of two ring candidates.
Shielded from outages
Five cache tiers serve recent answers while a backend recovers.
The contract
Routes are one to one: every component has exactly one page path and one API path.
teleon_hot_swap_binding/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/topology/ring | RING-3 | Read the route map and ring nodes | Listed |
GET | /v1/topology/routes/{component} | RING-3 | Read the page and API path for a component | |
GET | /v1/topology/cache | RING-1 | Read cache tier health |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/topology.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Hash ring
- A circle of hash values where each worker owns an arc, so work spreads evenly and moves little when workers change.
- Edge
- Servers close to the reader that answer requests quickly and pass the rest to the origin.
- Circuit breaker
- A switch per lane that pauses calls to a failing dependency and retries carefully once it recovers.