Boundary Node Roadmap

Roadmap
104

Hey @Gekctek

There are two parts to that:

  1. Discovering all API boundary nodes: To this end, you need to make a read_state and request the path /api_boundary_nodes/... (see interface spec here). This will return you all API boundary node IDs, their domains, their IPv4 addresses, and their IPv6 addresses. You can take a look at how agent-rs handles this here and here.

  2. Routing strategy/health checking: Once you have all API BNs, you need to decide how to route traffic to them. You could do something very simple like just randomly picking one or you could do some health-checking/latency measurements. To this end, you can call the /health endpoint of the API boundary node. If it is healthy, you will get a 204 status code (No Content) back. How you decide to route is then up to you. agent-rs measures the latency in addition to the health status and then prefers lower latency API BNs.

I hope this helps you getting started.

3 Likes