A presentation the describes the evolution and nature of mciroservices for use is distributed, service oriented architecture

1. @reselbob
Moving to
Microservices
Bob Reselman

2. @reselbob
Take the Survey
https://www.surveymonkey.com/r/L8DP5NY

3. @reselbob
Brief Bio

4. @reselbob
Brief Bio

5. @reselbob
Rule of the Road
• I am not Mr. Know-It-All nor do I play him on
TV
• Run time questions requesting clarification
are welcome
• Big Picture questions and opinions are
welcome at the end

6. @reselbob
Moving to Microservices
• What is a Microservice?
• Real World Example
• The Road to Microservices
• Evolutions of Deployment Units
• Evolution of SOA
• Architectural Guidelines
• Common Pitfalls
• Avoiding the Common Pitfalls
• Architecture
• Demo on AWS
• Next Steps
• Questions and Answers

7. @reselbob
What is a Microservice?
A microservice is a piece of semantically distinct logic embedded in a
fine grain deployment unit
Small autonomous services that work together, modeled around a
business domain
— me
— Sam Newman, ThoughtWorks

8. Real World Example

9. @reselbob
The Road to Microservices
You need to understand:
• The Evolution of Deployment Units
• The Evolution of Service Oriented Architecture

10. @reselbob
Evolution of Deployment Units

11. @reselbob
The Monolithic Application

12. @reselbob
Separating the Data Server

13. @reselbob
Separating the File System

14. @reselbob
Adding Virtualization

15. @reselbob
Adding Automated Deployment

16. @reselbob
Web Based Computing

17. @reselbob
The Arrival of the Container

18. @reselbob
Opaque Service Implementation

19. @reselbob
Evolution of SOA

20. @reselbob
A microservice is:
• Discrete
• Discoverable
• Focused on Consumption
• Responsible for its own data
• Ephemeral
• Immutable
• Scalable

21. @reselbob
Common Pitfalls
• Synchronicity
• State
• Storage
• Migrating Legacy Code

22. @reselbob
Avoiding the Pitfalls
Goal: Have multiple processes perform activities in a workflow

23. @reselbob
Avoiding the Pitfalls
Goal: Have multiple processes perform activities in a workflow
function getWorkFlow(){
const workflow = [];
const moesWork = getMoesWork();
workflow.push(moesWork);
const larrysWork = getLarrysWork();
workflow.push(larrysWork);
const curlysWork = getCurlysWork()
workflow.push(curlysWork);
return workflow;
}

24. @reselbob
Avoiding the Pitfalls
Goal: Have multiple processes perform activities in a workflow
function getWorkFlow(){
const workflow = [];
return getMoesWork()
.then(result => {
workflow.push(result);
return getLarrysWork();
})
.then(result =>{
workflow.push(result);
return getCurlysWork()
})
.then(result => {
workflow.push(result);
return workflow;
});
}

25. @reselbob
Avoiding the Pitfalls

26. @reselbob
Overcoming Synchronicity
Demo on AWS

27. @reselbob
Next Steps
• Understanding Discovery
• Supporting State and Storage
• Accommodating Legacy Code

28. @reselbob
Questions and Answers
Bob Reselman
reselbob@gmail.com