Forum Discussion
NimbostratusLoad Balancing best practice question
Here is a Load Balancing best practice question
Marketing has new idea to generate revenue. An Email will be sent out to My Company customers with My Company URL/branding. URL link will be My Company and customer will need to get to website at NOT My Company website. NOT My Company site will then offer discounts/coupons.
Option A URL link goes to My Company site. F5 does a redirect to NOT My Company site. DNS CNAME at My Company for NOT My Company IP Provide My Company certificate to NOT My Company site.
Option B URL link be a My Company DNS CNAME to NOT My Company IP. Provide My Company certificate to NOT My Company site. Removes need for redirect.
Option C My Company virtual server on F5 and have associated member point to NOT My Company website. Provide My Company certificate to NOT My Company site. Removes need for DNS CNAME.
Same SSL/certificate at My Company and the NOT My Company site to ensure good user experience.
3 Replies
Michael_YatesIf both sites are hosted locally behind the F5, you don't care about having multiple FQDN's pointed to a single Virtual Server, and you have a Multi-SAN SSL Certificate on the Virtual Server then I would go with Option C and use an iRule to split the traffic to separate pools based on the incoming HTTP::host value.
It is a cleaner solution with less construction and tear down, and it would be easy to redirect the traffic to your main site if your business should ever decide to dispose of it.
This is just my opinion though based on the information you provided.
Good luck with whatever option you choose.
russ_viaThanks very much for the reply. I wish it was all behind the same load balancer.
At "My Company site" we are using F5. The "NOT My Company" is at remote site where customer is using different load balancer.
- Michael_Yates
If it is hosted off-site, then I would suggest Option A to redirect the client away from you and directly to the hosting facility to remove any possible latency issues.
