A very interesting TPM Podcast with Vidya Vrat Agarwal on Microservices.  We talk about large enterprises moving from a monolithic application patterns on to microservices what that entails. We go on to talk about various microservices best practices. TPM Podcast with Vidya Vrat Agarwal on Microservices.
TPM Podcast with Vidya Vrat Agarwal on Microservices
This has been split into three eposodes:-

Part I: Lives here.
Part II: Lives here.
Part III: Lives here. 

Vidya’s LinkedIn Profile - https://www.linkedin.com/in/vidyavrat/

Also, read my previous post on microservices here :-

* https://www.mariogerard.com/microservices/ 
* https://www.mariogerard.com/building-resilient-microservices/ 

We talk about :- TPM Podcast with Vidya Vrat Agarwal on Microservices.

What is a microservice? TPM Podcast with Vidya Vrat Agarwal on Microservices.
Advantages of microservices
Monolithic applications vs microservices ?
Why is there is renewed uptick in organizations using Microservices ?
Pain points of microservices
How do you break down monolithic applications into microservices
Microservices Advanced Topics

Vidya's Interesting LinkedIn Posts TPM Podcast with Vidya Vrat Agarwal on Microservices.

* Microservices Architecture 
* Single Team Owned Service Architecture
* Building A CI/CD  Pipeline

Thank you ! Hope you enjoed it !
------------****************-----------
Vidya's Linkedin Post (Extract) TPM Podcast with Vidya Vrat Agarwal on Microservices.
Abstract
The microservices architecture style is an evolution of the Monolith SOA (Service Oriented Architecture) architecture style. The difference between the SOA and microservice approach is how these are being developed and operationalized. With every new technology addition, our responsibility also increases to be abreast of pros-and-cons the new member has, and the pain points it is designed to solve. TPM Podcast with Vidya Vrat Agarwal on Microservices.
Monolith
Think of any MVC pattern-based API codebase, where all your controllers and POJOs (Plain Old Java Objects) or POCOs (Plain Old C# Objects) were developed, build and deployed as a single unit, and for almost all the times a single data store was used for the enterprise. I.e. One database is housing all the tables for various responsibilities, for example, Customer, Payment,