A Microservices Application Architecture is considered one central component part of an overall Cloud Native methodology, and this implementation scenario is also helpful to understand how to adopt microservices.
The approach can also be considered an ideal way of implementing this architecture. For example containers are an ideal of deploying and managing microservices.
This Newstack article provides a great overview introduction to this approach, describing how Cloud Foundry can be used as the PaaS for a Cloud Native implementation, explaining how it can be used to implement stateless microservices.
Containers and Microservices
In particular there is a natural synergy between microservices and container technologies.
Bernard Golden provides three reasons why you should always run microservices in containers:
- Finer-grained execution environments
- Better isolation allows for component cohabitation
- Faster initialization and execution
Bob Familiar introduces microservices, discussing their architecture and outlining cloud deployment scenarios, exemplified by a live demo on Microsoft Azure. The Microsoft Academy also offers a webinar introduction - Exploring Microservices in Docker and Azure.
Pivotal describes the relationship between PaaS & Microservices, and offers a Cloud Foundry implementation, as they explain in Deploying a Microservices Architecture with Cloud Foundry, and describe how it can accelerate projects like new mobile applications.
This blog describes the difference between microservices and the traditional three-tier architecture application, implemented as microservices on a PaaS, and Pivotal offers a Netflix OSS implementation on Spring Cloud.