Inside Our Fastly Recovery Plan

Inside Our Fastly Recovery Plan

How we offer reliable site security

The purpose of our disaster recovery plan is to prevent downtimes with Amazon Web Service (AWS) that directly affect site reliability. We pride ourselves on our ability to reliably keep traffic flowing to our client's sites, even in the event of a disruption.

We partner with Fastly — our CDN provider — for our failover plan, which is based on rerouting traffic directly to our servers in case of an outage.

This Is the DNS Configuration for Clients During Normal Operation: ~> * ~> ~> origin (us-east-1)

When Fastly Is Unavailable, We Update the Configuration to the Following: ~> * ~> origin (us-east-1)

SSL Certificates Are Covered By:

  • SAN certificates provided by Fastly
  • Our in-house certificates

Origin Configuration

    ELB ~> EC2 instance (nginx ~> varnish ~> nginx ~> uwsgi ~> application)
  1. Nginx: SSL termination
  2. Varnish: Caching layers that duplicate the varnish configurations implemented for Fastly; it uses the same surrogate keys and the same TTLs
  3. Nginx: Connections pool
  4. Uwsgi: Application server

Every EC2 instance also has its own caching layer that allows it to effectively handle incoming requests. Fastly is a stable vendor, and we have never needed to move all of the traffic from the CDN to our side. However, last year, we did successfully handle a 25% switchover.

At the moment, we don't have any automatic failover systems. Amazon Route 53 is under the manual control of our operations team.

Data Centers and Points of Presence (PoPs)

Fastly operates an autonomous system with extensive connectivity relationships. This ensures that a single data center does not become reliant on a single network uplink. Because of this, our CDN can degrade gracefully when outages do occur.

While an outage of the central Fastly app may temporarily prevent us from making configuration updates, all of the Points of Presence (PoP) serving our clients' content operate independently. When an outage occurs in a single PoP, other PoPs continue to serve traffic normally. This ensures our users' requests are routed accordingly, and secures our clients' site reliability.

If you have more questions about our Fastly recovery plan, email or contact your account manager today.

Related Articles

What Is RebelMouse?
Request a Proposal
The Most Secure CMS of 2023

The Most Secure CMS of 2023

Why RebelMouse Is the Most Secure CMS on the Web

Delivering a secure, high-performing environment with extreme reliability is essential to all of our clients at RebelMouse. We only use industry-leading, reliable approaches to host our infrastructure. This ensures maximum stability and security for all of our clients’ data. Here are just some of the reasons we’re able to maintain a hard-bodied product that’s flexible, too.

Keep reading...Show less
Meet the RebelMouse Platform: The Highest Performing CMS on the Web
Rebel Insights

Meet the RebelMouse Platform: The Highest Performing CMS on the Web

Make sure your site is set up for success in 2022.

In the spring of 2020, Google let the world know that its Core Web Vitals would become the new benchmark for measuring a site's performance in its search results, known as the page experience update. Fast forward to more than a year later in August 2021 when, after much anticipation, Google's page experience update became official.

Since its rollout, developers have felt the impact of how their publishing platforms stack up against the new standard. Important decisions around the architecture of your site can now make or break your site's performance in the eyes of Google.

HTTP Archive, a tracking platform that crawls the web to identify trends and record historical patterns, frequently reports on how top content management systems (CMS) have weathered the page experience update through the creation of its Core Web Vitals Technology Report. RebelMouse has consistently outperformed major CMS platforms on Google's most critical metrics throughout the year:

Getting superior scores on Google's performance benchmarks isn't easy, either. The Ahrefs blog analyzed Core Web Vitals data from the Chrome User Experience Report (CrUX), which is data from actual Chrome users, to see how the web stacks up against Core Web Vitals. Their study found that only 33% of sites on the web are passing Core Web Vitals.

data from Ahrefs tracked on a line chart finds that shows only 33% of sites on the web pass Google's Core Web VitalsFrom Ahrefs.

Luckily, performing well on Core Web Vitals is possible with thoughtful, strategic changes to your site’s codebase. Here's what you need to know and how we can help.

Keep reading...Show less
Interested in a Free Website Health Check?Check Your
Website's Health
Get Your Free Analysis Now