search

openziti / fabric

Geo-scale overlay network and core network programming model
Apache License 2.0
49 stars 14 forks source link

Service Binding 2 #38

Closed plorenz closed 4 years ago

plorenz commented 4 years ago

Currently we try to derive binding based on address when creating services. Should we do that dynamically when being dialed? If not, we need to enforce service binding so that edge cannot bind a non-edge service.

michaelquigley commented 4 years ago

I'm not sure I'm following you. The binding is the binding. The address is the address. For plain fabric services, the binding is resolved and passed the address when dialing the termination of the service. The address needs to be in a format understood by the xgress component named by the binding.

The fabric should not understand anything about edge services. This sounds like something that should be layered on top of the fabric within the edge itself?

plorenz commented 4 years ago

This will be resolved by the work to extract terminators from services. See https://github.com/netfoundry/ziti-fabric/wiki/Pluggable-Service-Terminators