Microservices are an architectural style that structures an application as a collection of small, independent services that communicate with each other, often using lightweight mechanisms such as RESTful API calls. Each microservice runs in its own processes and focuses on doing a small, well-defined job, making the services highly maintainable, replaceable and scalable. The microservices architecture allows an application to more easily evolve and embrace new technologies.

1. About Microservices
Think small to go big
Salvatore Cordiano

2. One giant app that did everything

3. Three-tier architecture

4. Monolithic application
• Web assets (CSS, JS, Images, etc.)
• REST API
• Data Persistance tier
• Sessions
• Authentication
• Security
• …

5. The age of the monolith is over

6. What are microservices?
“Fine grained SOA”
Adrian Cockcroft, Netflix

7. What are microservices?
“The microservice architectural style is
an approach to developing a single
application as a suite of small services,
each running in its own process and
communicating with lightweight
mechanisms, often an HTTP resource
API”
Martin Fowler, ThoughtWorks

8. What are microservices?
Every microservice does one thing and
one thing well

9. Codebaseissmall

10. How small is small?
“Something that could be rewritten in
two weeks”
Jon Eaves, Real Estate Australia

11. Autonomous
• PaaS or own OS process
• Communication via network calls
• Black-box
• Application Programming Interface (API)

12. Technology heterogeneity

13. Embrace new technology

14. Resilience

15. Scaling

16. Ease of deployment

17. Composability

18. Optimizing for replaceability

19. Organization alignment

20. Disadvantages
• Network issues
• Distributed computing
• Authentication (SSO, Stateless, Mutual, etc.)
• Service discovery