Page History
...
Hub-and-spoke, single web client
Section | |||||||
---|---|---|---|---|---|---|---|
|
Hub's shrine.conf
Code Block |
---|
shrine { ... queryEntryPoint { ... } hub { ... downstreamNodes { "Node A" = "http://nodeA.example.com/shrine/rest/adapter/requests" "Descriptive name for node B" = "http://nodeB.example.com/shrine/rest/adapter/requests" "Human-readable name for node C (can be anything)" = "http://nodeC.example.com/shrine/rest/adapter/requests" } } // NB: no adapter { } block } |
...
This configuration creates a hub-and-spoke network with a single hub node H, and spoke nodes A, B, and C, with corresponding reduction in firewall openings and cert exchanges required compared to a fully-meshed network, while allowing nodes to expose their own web clients for political, branding, or other purposes.
Hub's shrine.conf
Code Block |
---|
shrine { ... hub { ... downstreamNodes { "Node A" = "http://nodeA.example.com/shrine/rest/adapter/requests" "Node B" = "http://nodeB.example.com/shrine/rest/adapter/requests" "Node C" = "http://nodeC.example.com/shrine/rest/adapter/requests" } } // NB: no adapter { } block } |
...
Overview
Content Tools