Join Chander Dhall for an in-depth discussion in this video Multiple technology stacks, part of Microservices and Azure Service Fabric Basics for Developers.
- [Narrator] One of the great advantages of the Microservices approach is being able to use the right technology, or the right framework, most suited to solve a particular problem. In case of a monolithic service, you are stuck with just one technology. Upgrading it means upgrading the entire stack to either a new version of the same technology or to a completely different technology. The latter requires a rewrite and is not always that easy.
With Microservices, we can even create the video service in, let's say, .NET. The photo service in, let's say, Java. Maybe the thumbnail service in Node.js, or any other technology of your choice. It also helps us with using the right technology for the right business problem. For example, if Node.js is good at I/O, or input/output, maybe we can use it for that part. For business domains that require a lot of computation, we may be able to use C, C++, or even a functional programming language, like F#, which is really good for computation.
Then, have it exposed via Microservice, to the Node.js app, or the microservice that's consuming it.
- 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