Join Chander Dhall for an in-depth discussion in this video No conflicting dependencies, part of Microservices and Azure Service Fabric Basics for Developers.
- [Instructor] Imagine there's a monolithic service that takes care of video, audio, photo, and thumbnail, and needs a text parser for the video description, metadata, and subtitles. It needs a text parser also for the audio part. What if the video part needs to upgrade to version four of the text parser library, while audio part may have a breaking change and doesn't want to upgrade at that moment? This is just one example to help you understand the problem of conflicting dependencies.
Dotnet developers traditionally call this problem DLL Hell. This could be a problem for only specific technology stacks, but microservices offer a solution that is easy to implement if architected right. So in this case, you can see that we have two different services, and they can depend on any version of the text parser. These are just a few reasons why microservices can make your life easier.
- 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