iheartradio / asobu Goto Github PK

Manage endpoints by sets (each service provide an endpoint sets), each set has a version and name(maybe same as root path?).

• A whole set can be offline if all backing service instance go offline, or they no longer support such version.
• New definition of endpoint set will replace the old set with the same name and version.
• For now does not support serving multiple sets with the same name (root path) but different version.

On the gateway side

1. path matching using PathBindable and extract parameters into record?
2. A record from json body and typed labels.
3. Authentication and sessionInfo
4. Construct the whole handler with all filters directives and so on
5. Send back to the ms one record

something wrong with the lazy initialization.

No cluster aware router needed any more.

This one might be blocked by kanaloa iheartradio/kanaloa#171

Bottom line: endpoint definitions only have ADTs of header enrichment commands. Per requests, gateway and service communicate with asobu.DistributedRequest and asobu.DistributedResult.
The DSL on the service side extract asobu.DistributedRequest into Domain classes.

Investigate the possibility of using varargs of tuples instead.

So that it's included in the build.

The rest endpoint and a particular service should not need to share the map of all endpoints. Only the rest nodes need this complete map. Between rest nodes and any given service, only a single distributed data register is required. Then a second data map can be shared across all rest nodes. This reduces the 'scope' of an endpoint and decouples each endpoint from one another, potentially decreasing their propagation time to the rest nodes and increasing their resiliency.