Join Chander Dhall for an in-depth discussion in this video Programming model architecture, part of Microservices and Azure Service Fabric Basics for Developers.
- [Instructor] Before we get into the programming model, it's important to understand the programming model architecture. As we've discussed earlier, we have two kinds of services. One is the stateful service and the other one is the stateless service. Azure Service Fabric allows you to create any type of service. It's important to understand that if you do want to take care of state by yourself, you are going to choose the stateless service template. In that scenario, you will be responsible to manage the state of your entire application.
And if you choose the stateful service template, Azure Service Fabric will give you tools to create state, maintain state. At the same time, it will automatically replicate your state amongst all nodes in that cluster. So you can see in the diagram that we have three different application types, and these are just three examples of application types. Application type one has stateful service one and then it has stateless service two.
You can see application type two might still be using the same service that application type one is using. In this case, that happens to be service two, which is a stateless service. And applications type three might be using two different services. One of them is service one and service three. That's exactly the entire point of microservices. The same service could be used in any application and is independent of any other service.
When it comes to the level of the service, it doesn't matter if it is stateful or stateless. It still has three components to it. One is the code, the other one is configuration, and the third one is data associated with that service. This is really a high level architecture of how your services are going to be part of your application with Azure Service Fabric facilitating your architecture. Here's a little bit more detail into the actual architecture.
So in this case you may have an application, application type one, and then you may have two different types of services. It really doesn't matter what service or what kind of service, but there are service types. Azure Service Fabric calls this particular layer as service type, and that's just part of their terminology. At any given point of time, you will have a service type. And at the level of the service type, you will have partitions. And in this case, we have two different partitions.
And every single partition will have instances of the same service that are going to be running. And in this case, we have three different replicas of the same service under each partition.
- Reviewing microservices vs. monolithic architecture
- Reviewing microservices and Azure Service Fabric basics
- Programming model architecture
- Creating a stateless service and a stateful service
- Creating a cluster in Azure
- Adding security to a cluster
- Finalizing cluster creation
- Deploying to an Azure cluster
- Debugging an application remotely