Microservice is about creating lots of small, distributed single purpose services, with each service owning its own data. This service and data coupling supports the notion of a bounded context and a share-nothing architecture, where each service and its corresponding data are compartmentalized and completely independent from all other services, exposing only a well-defined interface (the contract). This bounded context is what allows for quick and easy development, testing, and deployment with minimal dependencies. In this talk we will analyze the typical models of a microservice architecture. The talk does not simply want to explore what is good in this approach, but wants to highlight the wrong models that often reduce the benefits.