Re: Maximum size limitation of Diego apps' routes


Tim Lawrence <tim.lawrence1984@...>
 

Wouldn't it be better to use a single URL and implement the auth and separation in the app via token or something rather than by host URL? Or if you need to do that maybe have a micro proxy app per customer which has the main app registered as a service? It seems a lot of overhead to have that many routes per app

Sent from my iPhone

On 12 May 2017, at 16:48, Jason Huang <jasonxs.huang(a)gmail.com> wrote:

Daniel,

Our apps support multi-tenancy and our customers are enterprise customers. For each subscription, there is unique ur which is mapped to the same app. Therefore for 500 subscriptions there are 500 routes. This new limitation introduced in Diego would break our production.

Can someone share the reason for introducing the limitation?

Thanks,

Jason


On Fri, May 12, 2017 at 6:25 AM, Daniel Jones <daniel.jones(a)engineerbetter.com> wrote:
Hi Maggie,

That's an unusual number of routes for a single app. Could you explain the use case please, so we can attempt to think of other solutions to the problem?

Regards,
Daniel Jones - CTO
+44 (0)79 8000 9153
@DanielJonesEB
EngineerBetter Ltd - UK Cloud Foundry Specialists

On 12 May 2017 at 03:21, Meng, Xiangyi <Xiangyi.Meng(a)dell.com> wrote:
Hi,



We have one application with over 200 routes and one application with over 400 routes. And we expect more routes will be created with more subscriptions coming.



But those applications can’t run in Diego container due to the maximum size limitation of 4KB as mentioned in https://discuss.pivotal.io/hc/en-us/articles/230433388-Migrating-Applications-from-DEAs-to-Diego



Diego imposes a 4KB limit on the maximum size of an application's routes. While this doesn't translate to a specific number of routes, as it would depend on how many characters are in each routes, we are estimating that gives you space for 40 to 50 medium sized (50 character) routes. If you have too many routes bound to your application, you'll see the error Runner error: desire app failed: 503. In some cases you can work around this by using a wildcard route (i.e. *.my-domain.com) instead of mapping individual routes. When that is not possible, the only other option is to run multiple applications mapping 40 to 50 routes to each application.



Apparently wildcard is not an option and we don’t want to split applications just because we can’t add more routes. Is there any other solution? And would anyone help to explain why this limitation is necessary? I don’t remember same issue existed in DEA.



Thanks,

Maggie

Join {cf-dev@lists.cloudfoundry.org to automatically receive all group messages.