Copyright © RebelMouse 2019

Follow Us:

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

Publishers No Longer Have to Submit Their Site to Google News

Google's Publisher Center creates new opportunities for audience growth

Just before the start of the next decade, Google announced an important change to its Google News offering with the launch of Google Publisher Center. The new interface merges Google News Producer and Google News Publisher into one to streamline the partnership process for publishers.

Overall, the change should make it easier for publishers to manage their Google News settings, including updating themes, directing URLs to section pages, and configuring user permissions. Read the full list of features here.

Keep reading... Show less

How to Find Work-Life Balance as a Remote Employee

Tips from our CEO on making the most of an office-free lifestyle

Working from home is becoming increasingly popular, with an estimated 66% of companies now allowing remote work and 16% operating completely office-free. RebelMouse is one of those fully remote companies, and over the years we've mastered how to stay close to each other despite being spread across more than a dozen countries. We believe working remotely is good for both our personal lives and our productivity. Read more about this here.

Still, working free from the shackles of an office environment doesn't mean every day is a dance party in your pajamas from 9 to 5. Working from home comes with its own set of challenges just like any other job.

Keep reading... Show less

Inside RebelMouse’s Quality Assurance Operations

How We've Perfected Stress-Free Publishing

At RebelMouse, we like to refer to our enterprise publishing platform as "lean tech." Most publishers have a natural inclination to start doubling down on teams of developers who try to build unique experiences to help stand out above the noise. But they should actually be doing the opposite: Lean tech is the preferred way to cut through content saturation. By allowing RebelMouse to obsess over your product, content producers, editors, managers, and everyone in between can focus on creating quality content and taking advantage of opportunities to leverage distributive publishing strategies that create real revenue growth.

One of the major reasons we're able to maintain a lean tech environment is thanks to our approach to quality assurance (QA). We make updates to our platform daily to ensure our clients always have access to the most robust, high-performing, and secure version of our platform. Behind the scenes, this means having a solid QA structure that's efficient, creates less bugs, and catches the ones that do pop up before they go live. It's a system of checks and balances that's hard and costly to replicate on a custom CMS. Here's a glimpse into how it works.

Our Tech Stack Toolbox

  • Cucumber
  • Java
  • Junit
  • Maven
  • Selenium WebDriver
  • TeamCity
  • Zalenium (Selenium Grid)

Our Checks and Balances Workflow

Automated Regression Testing Cycle

The Lifecycle of a Product Update

When an update is first made to RebelMouse, TeamCity immediately triggers the start of automated tests to review integrity.

TeamCity Build

TeamCity Agent

The tests run in parallel on TeamCity's Build Agent. Next, Zalenium creates docker containers with browsers that matches the count of parallel threads. An Allure report is then generated from the test results, which shows the state of the application after the update.

Allure Report Pass

If a test doesn't complete successfully, the testing framework receives a video with a failed test and attaches it to the Allure report.

Allure Report Issue

Based on the report analysis, a QA specialist will create a "bug" ticket in our product management software to address the issue if needed. Then, information about the bug is immediately sent to the project manager and we begin the process of correcting the problem.

The media powerhouses we power can publish with confidence knowing that any product issues that arise are met with a tried-and-true process to fix the problem with little-to-no disturbance to their workflow. If you have any questions about this process, please email

Related Articles

Subscribe to Our Newsletter