A load balancer in production, does balance to each application or to the front-end server?
Hi there,
check these links to know more about it:
Hope it helps :)
Regards João
https://success.outsystems.com/documentation/11/setup_and_maintain_your_outsystems_infrastructure/setting_up_outsystems/possible_setups_for_an_outsystems_infrastructure/high_availability_and_scalability_strategies/
https://success.outsystems.com/documentation/11/setup_and_maintain_your_outsystems_infrastructure/setting_up_outsystems/recommended_configurations_for_load_balancing/
yes , I have had previously read these articles but no one says what i need to know or i can not extract from it. For instance, when it says : " In a farm environment, balancing the application load across multiple front-ends is a basic requirement to ensure higher availability" , what do you mean in "balancing the application" ? i can have 10 different applications in the same farm of 3 front end, each one with its different url , i mean, all with the same subdomain, second level domain and top level domain , but different subdirectory ... could i have, for each application , a load balancer ? or for all of them, 10 different application , one only load balancer pointing to the 3 front end?
From my intake and understanding of the documentation, the load balancer typically balances the incoming requests to the front-end servers rather than individual applications, being its primary purpose to distribute the traffic evenly across multiple servers to ensure optimal resource utilization and high availability.
Kind Regards,
João
And what about thinking in ensure availability to the differents deployments? In fact our loadbalancer acts as a reverse proxy , i was thinking in something like
https://success.outsystems.com/documentation/how_to_guides/infrastructure/using_outsystems_in_reverse_proxy_scenarios/common_use_cases_in_reverse_proxy_scenarios/?_gl=1*ux8yw1*_ga*OTAxMTU2MDczLjE2NzY0NTI4NzY.*_ga_ZD4DTMHWR2*MTY4ODM5MjI1OS43MC4xLjE2ODgzOTM3OTAuMC4wLjA.
and, each time , I should deploy one of them to production, follow a procedure as explained in
https://success.outsystems.com/documentation/11/managing_the_applications_lifecycle/deploy_applications/balanced_application_deployment/
Just to do not affect any application when another one is deployed, and ensure that all deployments are done great.
I am understanding your idea. Using a reverse proxy for load balancing different apps in different servers to segregate them and deploy each instance separately. I am unsure if you can achieve this, and maybe you could contact support for more info on this subject.
However, if done properly, the balanced deployment procedure in your second link, usually solves this problem.
Sorry I could not assist you more =)
Hi Roser,
That kind of behaviour that you're writing about can be obtained (or similar) with multiple pipelines:
You can read more about it here:
https://success.outsystems.com/documentation/11/setup_and_maintain_your_outsystems_infrastructure/setting_up_outsystems/possible_setups_for_an_outsystems_infrastructure/infrastructure_architecture_and_deployment_options/
You can check another discussion about that here:
https://www.outsystems.com/forums/discussion/49698/multiple-production-environments-for-separate-applications/
Hope this can clarify you!
Best regards,
Ricardo