Re: Feedback: A slightly different perspective on route services
James Bayer
we explored the ux of app to service binding in detail, but it is
toggle quoted messageShow quoted text
problematic. apps will soon support multiple routes on different ports. e.g. imagine an app with 3 ports: web traffic goes to container port 8080 on web.example.com admin traffic goes to container port 8888 on admin.example.com jmx goes to 9000 on jmx.example.com which of the 3 routes should the route service bound to the app be associated with? a route can be mapped to multiple apps, what happens when some apps mapped to a route have a route service bound and others don't? shannon can probably explain more of the problem areas that we discussed, i need to get to bed :)
On Thu, Jun 25, 2015 at 11:55 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:
This thread [0] on Route services has got me thinking. I'd like to --
Thank you, James Bayer
|
|