Join us for Failure is no option, September 15th - October 26th
We have a brilliant opportunity for you in the upcoming Failure is no option webinar series!
When deploying solutions/projects to the cloud one would think that resilience would always be taken into account. However, we regularly read articles in the press of organizations that are not as resilient as they thought they would be. Question is 1) What is the root cause? 2) How to assure resilience?
Let's start with defining RESILIENCE: Resilience is the ability of a system to respond to or recover from a crisis or disruption. So, when a customer faces a cyber-attack (eg. Belgium suffers major cyberattack – EURACTIV.com ) or the datacenter where the system is running becomes unavailable (eg. Millions of websites offline after fire at French cloud services firm | Reuters) how does that system respond and if response is not possible how can the system recover so that the organization can continue to operate with no or minimal disruption.
Where does this come from, what is the root cause? When moving to the (public) cloud many expect that resilience is built-in in the cloud platform. It's clear that especially public cloud providers have no choice but to take resiliency responsibilities very seriously. In the early days of the cloud and still today potential cloud users have concerns with infrastructures outside of the organizations direct control. Therefore, it's a no brainer that public cloud providers run datacenters that are state of the art. If they wouldn't take their resiliency responsibilities so seriously, they just wouldn't have a reason to exist. Read more on the Azure Global Infrastructure at Global Infrastructure | Microsoft Azure. Obviously the public cloud supports multiple customers and not every customer has the same requirements. Even within 1 organization multiple projects might have different requirements when it comes to resilience. The higher the resilience requirements the more protective measures need to be taken and as in (public) clouds one pays what one uses the cost is rising with the resilience requirements which is very normal as also in a on-prem world the cost is rising with rising resilience requirements.
Next question is how do we assure resilience? First is to recognize that "Resilience" has multiple aspects: Cyber-Security, High Availability, Scalability, Disaster Recovery, … and for each of these aspects’ solution architects need to make decisions that balance the resilience goal vs cost & operational excellence. In order to be able to take the right decisions it is clear that the architects need to understand 1) what resilience measures are taken by the provider 2) the options the cloud provider is providing to improve your resilience score.
The Microsoft Azure Well-Architected Framework provides technical guidance specifically at the workload level across five pillars - cost optimization, security, reliability, performance efficiency and operational excellence. Partners can leverage this guidance to enable customers to design well-architected and high-quality workloads on Azure.
In order to further guide the architects in our Partner Ecosystem the Belux Partner Tech Team is launching an initiative called " Failure is no option". Through a series of webinars, we'll provide you with our insights on how to improve the Resilience Score for each of your deployments.
The Failure is not an option’s session calendar is the following:
- Session 0: Introduction to the Azure Well-Architected Framework Partner Journey (27.09.2021 13:00- 14:00)
- Session 1: Introduction to Failure is no Option (FINO) (15.09.2021 15:30-17:00)
- Session 2: Approaching migration modernisation (28.09.2021 15:30 - 17:00)
- Session 3: The call for more elements and observability. (5.10.2021 15:30 - 17:00)
- Session 4: Rub some DevOps and Security on it (12.10.2021 15:30 - 17:00)
- Session 5: Principles of cost optimization (26.10.2021 13:00 - 14:00)
Don't forget to register!