{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Fthenewstack.simplecast.com%2Fepisodes%2Fmicroservices-in-the-cloud-native-world-m2gYV3_r","width":444,"version":"1.0","type":"rich","title":"Microservices In the Cloud Native World","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/5672b5/5672b58f-7201-4e0e-b0af-da702259d97f/429b01bf-9c44-4c44-b61f-43af61ac9639/avatars-000115856938-s0r47h-original.png","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/429b01bf-9c44-4c44-b61f-43af61ac9639\" height=\"200\" width=\"100%\" title=\"Microservices In the Cloud Native World\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"Have you ever tried to explain microservices to anyone? Depending on the context, people explain it differently. But when it comes to establishing the relationship between microservices and Cloud Native, no one explains it better than Mark Russinovich, CTO of Microsoft Azure.\n\nAccording to him, the best way to understand microservice infrastructure is to look at the previous generation architecture of client-server era. The era of monoliths. Typically, there were three tiers: application (front end); the middle tier (business logic) and then the third tier of backend for things like database server.\n\nThis model slows everything down. You can’t innovate because all three tiers need to be in sync with each other. Trying to be agile by embracing cloud means on-demand creation of computing resources. It breaks the older model. You end up with a mismatch between the delivery model of the application architecture and what the underlying platform can provide.\n\nWatch on YouTube:  https://youtu.be/9rG8en7Po00"}