Service Oriented Architecture

A talk on SOA as done at Voiceworks BV in Almere on August 6th

Transcript

1. SERVICE ORIENTED ARCHITECTURE CHALLENGES AND OPPORTUNITIES
3. SOA?
4. A service-oriented architecture (SOA) is an architectural pattern in computer software design in which application components provide services to other components via a communications protocol, typically over a network.
5. components provide services to other components
6. via a communications protocol
7. via a communications protocol typically over a network
8. SOA != WEB SERVICES
9. SOA IS NOT ABOUT CODE
10. SOA IS NOT ABOUT CODE NOR IS IT ABOUT TECHNOLOGY
11. SOA IS ABOUT COMMUNICATION
12. SOA IS ABOUT FLEXIBILITY
13. SOA IS ABOUT RESPONSIBILITY
14. SOA IS ABOUT ABSTRACTION
15. LET'S ORDER A PIZZA
16. LET'S ORDER A PIZZA
17. NOW WHAT?
18. OLDSCHOOL
19. THE MOST COMMON SOLUTION
21. THE MOST COMMON SOLUTION
22. MICROSERVICES?
23. MICROSERVICES The definition of a service, microservice, macroservice, mediumservice or even a moderatelylargeservice seems to vary wildly depending on who you talk to. Hailo @ https://sudo.hailoapp.com/services/2015/03/09/journey- into-a-microservice-world-part-2/
24. MICROSERVICES The microservice architectural style is an approach to developing a single application as a suite of small services … these services are built around business capabilities and are independently deployable — Martin Fowler
25. BACK TO OUR PIZZA
26. BEFORE YOU START
28. START BUILDING
31. THE RIGHT TOOL?
32. ANOTHER EXAMPLE
33. HOSTING PROVIDER
34. HOSTING PROVIDER ▸ Use skills that are available ▸ Use tools that make sense
35. DON'T KNOW THE RIGHT TOOL?
36. PROTOTYPING
37. PROTOTYPING IS NOT ABOUT DEVELOPMENT
38. PROTOTYPING IS ABOUT LEARNING
39. FAILURE IS LEARNING
40. FAILURE IS OK
41. CONCLUDING ▸ Building applications is easy ▸ Building GOOD applications is hard ▸ Plan before you build. THINK before you build ▸ Accept failure early on to prevent failure later on
42. THANK YOU