if you’re app embedded, there’s no need for the router-embedded tunneler because you don’t need a tunneler at all. However, if you’re going to run a tunneler, there are some advantages to using the router-embedded tunneler, specifically on the hosting side. The benefits are mostly around simplifying deployments.
You generally want/need one or more routers in your hosting site. If you use the embedded tunneling functionality, you don’t need an extra tunneler running externally. You also bring the fabric one hop closer to the hosting server. Because of that, it’s also likely to be the most performant option (though as with anything, testing to get actual performance numbers is a good idea).
In terms of functionality on the hosting side, anything you should be able to do with one, you should be able to do with the other.
For client side, ziti-edge-tunnel (or any of the desktop edge or mobile edge components) is recommended because the router is a relatively heavy component. On the hosting side it’s not an issue because you will generally have routers sitting next to your server components anyway
I remember noticing this comment in one of the earlier threads.. so that answers my question re the tunneller binding.. as its not needed if you use app embedded networks.. but is if you dont
