Containers, Docker, Kubernetes, and Serverless are often used when explaining a Microservices architecture. However, focusing on physical deployment is missing the point of Microservices entirely. Microservices (or any size services) are about the logical separation and not about the physical deployment. Deployment flexibility is a by-product have having well defined boundaries for services that are autonomous.

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

Shout-out to new Members!
Wisconsin .NET User Group (https://www.meetup.com/Wisconsin-Net-Users-Group/)
Chuck Bryan

📝 Blog: https://codeopinion.com

📚 Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

0:00 Intro
0:27 Microservices Defined
4:12 Monolith
5:59 Logical vs Physical
6:38 4+1 Architectural View Model

#microservices #docker #domaindrivendesign

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#microservices #docker #domaindrivendesign #kubernetes #containers

Do Microservices require Containers/Docker/Kubernetes?
1.05 GEEK