Read this article to learn 3 lessons from the biggest outages of IBM Cloud, T-Mobile, and GitHub. The second quarter of 2020 was marked by several serious outages at prominent services including IBM Cloud, GitHub, Slack, Zoom and even T-Mobile (Source: StatusGator Report).
Nobody is immune from outages but it’s better to learn from other’s mistakes than from your own. The second quarter of 2020 was marked by several serious outages at prominent services including IBM Cloud, GitHub, Slack, Zoom and even T-Mobile (Source: StatusGator Report). I’m sure you noticed these outages like our team did. I decided to share the lessons we learned from this downtime, hoping we can all grow from it.
Having a status page helps to communicate with clients and keep them abreast of changes. This is a reliable and efficient tool. Status pages help clients and teams. Also, they can reduce support tickets because users will know what’s happened. Put simply, the status page is a convenient, efficient and necessary communication tool. But it becomes useless if you host it on your own infrastructure. It is advised to host your status page on a separate domain.
On June 10, 2020, IBM Cloud had an outage that impacted its general cloud services: Kubernetes Service, Cloud Object Service, VPN for VPC, Identity and Access Management (IAM), Continuous Delivery, App Connect, Watson AI and… their status pages. Fortunately, this page was available in the early stages of the outage and became available intermittently later. But in general, a lot of users criticized IBM on social media because of a lack of transparency and lack of communication. So, we can draw the first conclusion.
Hosting the status page on your own infrastructure can be dangerous for your reputation because of negative users’ impressions. It’s also quite useless because, in the event of downtime, it won’t be available – just like the rest of your services.
Of course, set up a status page.
There are three services they can use for status pages:
If you are smaller than IBM take a look at Cachet. This is an open-source tool. It’s pretty good and easy to deploy to any number of providers like DigitalOcean.
Mismanagement of multi-cloud expense costs an arm and leg to business and its management has become a major pain point. Here we break down some crucial tips to take some of the management challenges off your plate and help you optimize your cloud spend.
DevOps and Cloud computing are joined at the hip, now that fact is well appreciated by the organizations that engaged in SaaS cloud and developed applications in the Cloud. During the COVID crisis period, most of the organizations have started using cloud computing services and implementing a cloud-first strategy to establish their remote operations. Similarly, the extended DevOps strategy will make the development process more agile with automated test cases.
To move or not to move? Benefits are multifold when you are migrating to the cloud. Get the correct information to make your decision, with our cloud engineering expertise.
Long story short: Jekyll is a template engine changing markdown documents on static HTML webpages, that you can then host anywyere, because you don't need databases or server that has PHP or Python.
A common challenge that cloud native application developers face is manually testing against inconsistent environments. GitHub Actions can be triggered based on nearly any GitHub event making it possible to build in accountability for updating tests and fixing bugs.