Join Chander Dhall for an in-depth discussion in this video Independent scalability, part of Microservices and Azure Service Fabric Basics for Developers.
- [Narrator] Microservices is an architecture in which the goal is to create smaller isolated services that can deploy and scale independently. Let's talk about the promises of the microservices-based architecture. Microservices can scale independently. Imagine a monolithic video service that has some pictures and some thumbnails attached to it. After sometime the service may need hundreds of thousands of videos, and the video part of the service might need to scale.
However maybe for some reason, the thumbnail is not being used as much as the video or even the picture part of the service, or the utility for pictures is to be used by a completely different application. Having all three of these in one service makes it hard for this monolithic service to scale. In the microservices approach, all three would be independent of each other.
Something like this. In this particular case, we have four instances of the video service, two of the photo service, and is just one of the thumbnail service. What happens if for some reason we have an increase in users who want to just use the thumbnail service, or we have a completely different set of services increasing the traffic to the photo service tenfold. It doesn't matter.
In the microservices approach, all these services could be scaled independently of each other, and we can have 20 instances of photo services, in this case, if needed. Similarly, thumbnail service could be scaled up or down as needed.
- 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