- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
Amazon Web Services and Latency Based Routing
Monday, March 26, 2012
CITYTECH Managed Services clients who utilize Amazon Web Services DNS offering, Route 53, can benefit from extremely durable and cheap load-balancing between regions, including Europe and South America.
To understand this offering let's take a typical Adobe CQ5 web experience management configuration on Amazon Web Services. If the architecture requires availability between multiple regions, typically west coast and east coast, you would put a caching (dispatcher) and rendering (publisher) instance set in both regions. Amazon Elastic Load Balancer (ELB) is unable to route traffic between regions. Therefore, in order to distribute traffic between instances you would need a DNS provider to do your load balancing such as Neustar.
Working much the same way a content delivery network does Route 53 provides Latency Based Routing (LBR.) Site traffic is routed to the customer from the server with the least latency providing a faster load time of content, regardless of the region of the instance. As Route 53 is an extremely cheap DNS provider this can often save clients significant money.
An architecture utilizing multiple cloud vendors will need to engage a DNS provider for global load balancing.
In any scenario, CITYTECH has the expertise to implement global load balancing for your architecture.
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6
- Why You Should Get the WCM Experts Involved Early