Rapid Stabilisation / Case Introduction

“Why did my digital commerce platform not scale up even though we were previously experiencing low activity?” is a typical question we hear from “future customers”. Usually when they get into deep trouble when their digital commerce platform crashes and couldn’t be brought back up quickly.

Looking at the 10 biggest digital commerce sites, yearly downtimes of <10 minutes are standard, but already the 30th biggest site only had an availability of around 99,5% or >40 hours of downtime.*

Individual outages within this group of “global leaders” took between 1-30 minutes, which means the restoration time was very low.

We know from our experience that the reality looks very different for many average sized B2C or B2B digital commerce sites. Yearly downtimes accumulate quite often to >200 hours and individual outages quite often are 4 hours and in some cases even 24-48 hours long.

In this case study we will show how, in a good case, platform stability was achieved with one of our customers during an unexpected peak time (COVID-19 Crisis). We’ll compare it to a case where we executed a “Rapid Platform Stabilisation project” after a series of outages occurred at a 200m+ EUR B2B digital commerce site.

The Good Case: Stabilising through Corona Peak Load

The “Not so good” Case: Rescuing a Burning Platform

Mindcurv manages Digital Commerce & Content Platforms that generates >2,5bn EUR annual revenue and connects >3m IoT devices.

We serve global and local market leaders as well as digitally focused niche players.

Some customers we have supported

*Sources: Pingdom article on medium