Checklist: Web Application Resilience

Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/945453

Contents of this Issue


Page 0 of 0

Checklist WEB APPLICATION RESILIENCE dyn.com 150 Dow Street, Manchester, NH 03101 USA @dyn 603 668 4998 Given how critical website and applications have become to supporting revenue and productivity, there is nothing more important for your business than ensuring that your digital assets are reachable at all times. Consider the impact of latency and downtime on your business: customer loss, brand reputation damage, or permanent loss of revenue. Start with a complete internet resiliency architecture, and here's a 4-step checklist to get you on your way: Redundant Endpoints Before you can even think about failing over, you need to have an on-premises (in a secondary data center) or cloud-based alternative endpoint in place. Once you've implemented this, you can look at the choices you have available in your site failover architecture. Site Failover Whether it's to address performance and latency issues, or when you lose a site completely, the same DNS technology can reroute traffic to an available endpoint. If your primary site isn't available, it's important to be able to reach an alternate site rapidly and seamlessly. With an Active Failover service, you have a choice of configurations at your disposal to ensure business continuity. You may choose a primary-primary failover strategy or a primary-secondary approach—or you may even choose a primary-hidden secondary. Load Balancing and Traffic Steering Traffic steering services are helpful when you want to enhance web application performance or availability. When do certain load balancing and traffic management policies belong at the user edge and not at your local load balancer? And how is that decision made? You can choose from ratio/round robin, edge resiliency, geolocation, performance, or security approaches. DNS Failover Even if you have a redundant site and a failover plan in place, it will not ensure that users can reach your content. If the DNS server is not available, you'll need a secondary DNS solution--one that complements your existing DNS service, whether it's managed on-premises or via another managed DNS provider, supplying resiliency at the DNS layer if your primary DNS service suffers an outage or is attacked. It reduces the risk of losing critical services while also protecting against connection delays. Web content resiliency is critical to digital success, so make sure that you're ready. Establishing a highly resilient infrastructure that covers every vulnerability and eventuality is challenging. The good news is that you can accelerate the process by working with experts and incorporating the right services. Copyright © 2018, Oracle and/or its affiliates. All rights reaserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. 1044

Articles in this issue

Links on this page

view archives of eBooks - Checklist: Web Application Resilience