I recently spoke at API Days Australia about my experiences building distributed systems and some challenges my team faced deploying and running them on the edge.
It is not an exaggeration to say that most modern systems that teams build are running on the cloud in a distributed architecture. There are some well-known successful practices around DevOps for these cloud native solutions as well. But what happens when you want to use the same workflows to deploy and run on the edge where connectivity might be intermittent or not available (air gapped systems)?
How do we run Kubernetes on the edge and use our favourite GitOps workflows? In this talk we spoke about some of the techniques and practices we have been using to build and run workloads on Azure Edge and other edge devices. During this talk we elaborated on the challenges faced running Kubernetes on the edge and some practical solutions, starting off from your development environment, to continuously having your code deployed and running on a fleet of devices in an automated way regardless if it’s a mobile platform, drone or a submarine.
My team at Microsoft CSE (Commercial Software Engineering) have been building software that run on Kubernetes on the edge. This has posed a plethora of challenges and edge cases for us to solve.
In this talk we dived in to the best practices and practical solutions we have discovered along the way. This will help any team building software systems to run on edge devices that have intermittent connectivity or no connectivity (air gapped).
About API Days
This is the fifth time I spoke at API Days and I wanted to get my dev crew from the Microsoft Commercial Software Engineering involved in the talk. So I reached out to the organising committee and they gave us the green light to present this as a team. We were thrilled as this was the first in person conference for us since the Covid restrictions. We hope you liked the format we presented it in.
Recording & Slide deck
If you have any thoughts or comments please leave them here. Thanks for taking the time to read this post.