Microservice Architecture introduction and use Spring-Boot, Docker to implement microservice

1. Microservice
Architecture
RICH

2. Monolith
http://odino.org/on-monoliths-service-oriented-
architectures-and-microservices/

4. • Microservices - a definition of
this new architectural term
James Lewis
Martin Fowler

5. Microservice
• 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. These
services are built around business capabilities
and independently deployable by fully automated
deployment machinery. There is a bare minimum
of centralized management of these services,
which may be written in different programming
languages and use different data storage
technologies

6. Microservice
• 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. These
services are built around business capabilities
and independently deployable by fully automated
deployment machinery. There is a bare minimum
of centralized management of these services,
which may be written in different programming
languages and use different data storage
technologies

7. Microservice
• 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. These
services are built around business capabilities
and independently deployable by fully automated
deployment machinery. There is a bare minimum
of centralized management of these services,
which may be written in different programming
languages and use different data storage
technologies

8. Microservice
• 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. These
services are built around business capabilities
and independently deployable by fully automated
deployment machinery. There is a bare minimum
of centralized management of these services,
which may be written in different programming
languages and use different data storage
technologies

9. Monolithic
http://www.coscale.com/blog/comparing-microservices-and-monolithic-applications-from-the-perspective-of-
monitoring

10. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

11. Monoliths Microservices

12. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

13. Melvyn Conway
Any organization that designs a system
(defined broadly) will produce a design
whose structure is a copy of the
organization's communication structure.

15. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

16. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

17. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

18. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

19. Polyglot programming /
persistence

20. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

21. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

22. Characteristic
• Componentization via Services
• Organized around Business Capabilities
• Products not Projects
• Smart endpoints and dumb pipes
• Decentralized Governance
• Decentralized Data Management
• Infrastructure Automation
• Design for failure
• Evolutionary Design

23. Microservice Java
Framework
Dropwizard

24. http://blog.takipi.com/java-bootstrap-dropwizard-vs-spring-boot/

25. Demo
Code: https://github.com/RICH0423/Spring-Boot/tree/master/SpringBoot-
Jersey-Swagger-Docker

26. Reference
http://www.martinfowler.com/articles/microservices.html

27. Thanks