This document discusses microservices and provides an overview of the topic in 5 sections. It begins by defining microservices and their characteristics. Next, it compares monolithic architectures to microservices, noting that microservices allow for greater scalability, flexibility and easier deployment compared to monolithic applications. The document then covers some of the challenges of implementing microservices before discussing when and where they should be considered for an application. It recommends microservices when applications need flexibility, cost-effectiveness and scalability. It also suggests deploying microservices in the cloud.
3. Contact & Follow Me
3
Gmail : yachen1023@gamil.com
IBM : yachen@tw.ibm.com
Facebook : https://www.facebook.com/vincent.chen.184007
LinkedIn : https://www.linkedin.com/in/vincent-chen-78232368/
Twitter : https://twitter.com/yachen1023
LINE : yachen
4. 4
Agenda
4.When to consider microservices
- The needs for application
5.Where to roll out microservices
- The Cloud
1.What are microservices
- What are microservices
- Characteristics of a microservices application
2.Why microservices
- What came before - the monolithic architectural
style
- Monolithic vs. Microservice
3.How to get microservices in practice
- Challenges of microservices
- Service mesh
- DevOps
11. Monolithic
single code base for the entire
application
Microservice
Multiple code bases; each
microservice has its own
Monolithic vs. Microservice
11
Code
12. Monolithic
Can be confusing; hard to
maintain
Microservice
Better readability; easier to
maintain
Monolithic vs. Microservice
12
Clarity
24. Take away
24
What are microservices?
Why microservices?
How to get microservices in practice?
When to consider microservices?
Where to roll out microservices?