Watch videos with subtitles in your language, upload your videos, create your own subtitles! Click here to learn more on "how to Dotsub"


0 (0 Likes / 0 Dislikes)
>> In this video, we're going to talk about the benefits of loosely coupled architectures. As you may or may not know, typically Azure solutions are built using multiple services or components that send and receive data to one another. When you're building complex systems, it's best to loosely couple those services or components in your solution. You're probably asking, "what does it exactly mean when we say loosely coupled?" Each of the individual components in your solution has little to no knowledge of the definitions of the other components. These components simply need to send and receive data. They don't need to know about how that data's created or processed by the rest of the system. However, these components do need to agree on a standard for communication. So, they need to be loosely coupled, but why is loosely coupling your Azure services so important? First, loosely coupled services can be updated independently. Meaning that you, as a developer, can make changes as long as the communication strategy stays consistent and the Azure development team can continue to update and improve features and performance, without breaking the existing Azure solutions. It also allows services to be replaced without significant impact to the rest of the system. For example, imagine a faster storage option was released. If that new storage component could understand the same data, and send and receive standard messages, it could be changed without replacing or updating other components in your solution. Next, loosely coupling components allows you to add to your solution with ease. For instance, if you recognize a need to do data processing before storage, you can change your data messaging flow to route through a new component that processes the data and sends it back to your storage services. All this with minimal updates required. And lastly, loosely coupled services can be scaled proportionally to the amount of data traffic. It allows you to manage performance and cost on services independently. So this means you can scale up or scale out only the services that would truly benefit from the additional resources, and avoid paying for resources you are not using.   Loosely coupling your Azure services isn't just a great idea, it's a fundamental to Azure's data communication strategy. So make sure to take advantage of Azure standard messaging strategies designed to help your architecture manage and scale a great cloud solution.

Video Details

Duration: 2 minutes and 34 seconds
Language: English
License: Dotsub - Standard License
Genre: None
Views: 7
Posted by: csintl on Aug 29, 2018


Caption and Translate

    Sign In/Register for Dotsub above to caption this video.