Join Chander Dhall for an in-depth discussion in this video Scale of development, part of Microservices and Azure Service Fabric Basics for Developers.
- [Narrator] Scale of Development. Since these services are independent, we can now scale our development efforts. We can now have two, or even three different teams work on these services independently. If this was a monolithic service, the team had to hire people who can code for videos as well as pictures. However, in case of Microservices, developers working on the photo and thumbnail services may not even need to know how video works.
This makes our search for developers a lot easier, and we can scale development teams faster than ever. Making changes to a big service with too many moving parts might not be easy, and future releases might delay too. On the other hand, the Microservices approach not only helps with faster deployments, it also helps us with scaling our development efforts. In the previous diagram, the services were internal to the application network.
However, we can also expose the services individually. We can do this using a REST API. We can also use a common gateway for all the REST APIs within the corporation. The major benefit of this approach is optimal utilization of resources, as well as independent scaling.
- 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