Versions Compared

Old Version 27

changes.mady.by.user Bill Simons

Saved on

compared with

New Version 28

changes.mady.by.user Rachel Eastwood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Hub-and-spoke, single web client

Section
Column
width200px

 

Column

This configuration creates a hub-and-spoke network with a single hub node H, and spoke nodes A, B, and C. A single web client is exposed at the hub; queries originate and terminate at the hub. The spoke nodes only respond to queries.

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
}
 
Here, we have a shrine.queryEntryPoint block (so that queries may originate at the hub), and a shrine.hub.downstreamNodes block, so the hub knows who to broadcast queries to. The hub does not have a shrine.adapter block, since it's not queryable.

Each spoke's shrine.conf

Code Block
shrine {
  ...

  adapter {
    ...
  }
}

...