/explore
|
You are here 
|
platformengineering.org | ||
| | | | |
sookocheff.com
Disaster events are one of the biggest challenges that a software organization can face. Natural disasters like earthquakes or floods, technical failures such as power or network loss, and human actions such as unauthorized attacks can disable an entire fleet of systems, leading to complete failure for a business. To deal with disaster scenarios requires a proactive approach to prepare and recover from failure. One of the key benefits of running in the cloud is how easy it is to run workloads in multiple regions. This allows you to deploy a resilient architecture that supports disaster recovery, even in the cases where an entire region is disabled. |
|
| | | | | ||
| | | | |
jreypo.io
In the article about Kubernetes on ACS I briefly touched the topic of Kubernetes Ingress, originally I was going to made a post about Ingress however I thought it woud be better to explain the different methods to expose a Kubernetes based app and how are they implemented on Azure. |
|
| | | | | ||
| | | | |
blog.willemmelching.nl
Using Kubernetes for a small startup adds some complexity, but also has many advantages such as scaling and easy CI/CD. In this post we'll explore a simple AKS Kubernetes setup on Azure using Terraform serving a static page over HTTPS. |
|
| | | | | ||
| | | | |
haim.dev
When you need to run something just once, but on each node |
|
| | | |||
