Over the last few years, Docker and software container systems have become the industry standard for packaging and deploying applications. A consequence of this trend has been the development of container orchestration systems like Kubernetes and Apache Mesos. Microsoft Azure has entered the space with its own comprehensive system orchestration and management system, Azure Service Fabric.
What exactly is the value-add for Service Fabric? How do we use it to solve container-related technical challenges? This course answers both of those questions and goes even further by covering a number of relevant software design concepts. From this course, you will learn what Service Fabric does, how to use it to deploy a real application, and how Service Fabric incorporates design patterns and structures such as the actor model and collections.
By the end of the course, you should be ready to work with a team using Azure Service Fabric to create a working application.
Learning Objectives
- Use Azure Service Fabric to solve infrastructure orchestration challenges
- Learn about software concepts relevant to Service Fabric, including collections, the actor model, and stateful vs stateless services
- Deploy an application to a Service Fabric cluster
Intended Audience
- People looking to build applications using Microsoft Azure
- People interested in container orchestration systems
Prerequisites
- General knowledge of IT architecture
- General knowledge of software containers
Links
Welcome to section two. In this part of the course, we're going to cover a number of concepts that are important to making use of Azure Service Fabric. Not only will these concepts help you use Service Fabric successfully, it'll also help solidify your understanding of cloud application architecture more generally. This section is particularly important for people who don't have a lot of programming experience. If by chance you have built a lot of applications on your own, then a lot of this section may feel like review. Feel free to watch at two-times speed. I won't be offended.
The three main concepts we'll cover are as follows. One, stateless versus stateful services, two, the actor model, and three, collections. Each will get its own lesson. By the end, you should have a strong theoretical grounding for the hands-on work to be done in the final section.
So if you're ready, let's begin by learning about stateless and stateful services. See you there.
Jonathan Bethune is a senior technical consultant working with several companies including TopTal, BCG, and Instaclustr. He is an experienced devops specialist, data engineer, and software developer. Jonathan has spent years mastering the art of system automation with a variety of different cloud providers and tools. Before he became an engineer, Jonathan was a musician and teacher in New York City. Jonathan is based in Tokyo where he continues to work in technology and write for various publications in his free time.