A Pragmatic Approach to Microservice Architecture: The Role of Middleware

58 %
42 %
Information about A Pragmatic Approach to Microservice Architecture: The Role of Middleware

Published on January 27, 2016

Author: wso2.org

Source: slideshare.net

1. A Pragmatic Approach to Microservice Architecture the role of middleware Asanka Abeysinghe Vice President – Solutions Architecture, WSO2,Inc. @asankama http://asanka.abeysinghe.org

2. 2

3. 3

4. Enterprise today 4

5. In the process of moving to.. 5

6. Completely new pattern ? - Before identifying MSA as a pattern - In 2011, a service platform in healthcare - New service = NEW service container - 80+ service containers - Shell scripts and Maven to build containers 6

7. Platform 3.0 : evolution of middleware 7 Platform 1.0 - Mainframe and before  : centralized computing Platform 2.0 - Messaging, object orientation, SOA, EDA : distributed computing and internet Platform 3.0 - Platform 2.0 + next-generation middleware : the cloud

8. Microservices : our generation 8 Picture credit ; flicker

9. Microservices : new generation 9 Picture credit ; flicker

10. Microservices : reality (what I think) 10 Picture credit ; flicker

11. 11 http://www.pwc.com/us/en/technology-forecast/2014/cloud-computing/features/microservices.jhtml

12. 12 http://www.pwc.com/us/en/technology-forecast/2014/cloud-computing/features/microservices.jhtml

13. 13 Microservice architecture (MSA) is a pattern for building and delivering service-oriented applications with two primary objectives: agility of delivery and flexibility of deployment. 
 Source : Gartner

14. 14 MSA is not based on all-new architectural principles; it combines SOA best practices with modern application delivery tooling and organizational disciplines. Source : Gartner

15. 15 "Micro" is a concept of scope rather than size. Source : Gartner

16. 16 A microservice must have a single purpose and be loosely coupled in design and deployed independently of other microservices. Source : Gartner

17. MSA : reference architecture 17 Source : Gartner

18. MSA : characteristics 18 -  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 James Lewis Martin Fowler http://martinfowler.com/articles/microservices.html

19. Componentize as services 19

20. 20 Provide high-performance, functional rich, lean service containers to deploy services.

21. Organized around business capabilities 21 Picture credit ; http://martinfowler.com/articles/microservices.html

22. 22 Source : connected company – Dave Gray

23. 23 Provide a platform for pods to build and expose services.

24. Platform for digital transformation 24

25. Products not projects 25 Product line to frontline. Source : connected company – Dave Gray

26. 26 Provide end-to-end middleware capabilities.

27. 27

28. Smart endpoints and dumb pipes 28

29. But it leads to ….... 29

30. 30 Support bus/broker architecture.

31. EIP (enterprise integration patterns) 31

32. MSA : extended with bus/broker 32

33. Decentralized governance 33 Not every problem is a nail and not every solution is a hammer.

34. Platform 3.0 34 Mobile, social, store Event driven, IoT Bigdata, analytics DevOps Iterative Cloud native Open source API driven { } Polyglot programming QoS

35. 35

36. Decentralized data management 36 Picture credit ; http://martinfowler.com/articles/microservices.html

37. Platform 3.0 37 Mobile, social, store Event driven, IoT Bigdata, analytics DevOps Iterative Cloud native Open source API driven { } Polyglot programming QoS

38. Infrastructure automation 38 Picture credit ; http://martinfowler.com/articles/microservices.html

39. Platform 3.0 39 Mobile, social, store Event driven, IoT Bigdata, analytics DevOps Iterative Cloud native Open source API driven { } Polyglot programming QoS

40. 40 Automated testing 
 Continuous integration
 Support for containerization
 Support for devops automation
 Support for distributed deployment
 Lean, independent runtime

41. Design for failure 41

42. Platform 3.0 42 Mobile, social, store Event driven, IoT Bigdata, analytics DevOps Iterative Cloud native Open source API driven { } Polyglot programming QoS

43. Evolutionary design 43

44. Platform 3.0 44 Mobile, social, store Event driven, IoT Bigdata, analytics DevOps Iterative Cloud native Open source API driven { } Polyglot programming QoS

45. 45 Pluggable, extensible middleware architecture.

46. Phase layered strategy : platform 46 New Ideas Be*er Ideas Common Ideas I don’t know exactly what I want. I need to experiment. I know what I want, but it needs to be different from my compe@tors. I know what I want and it doesn’t have to be unique. Systems of Innova@on Differen@a@on Record PlaGorm Business Domain Services [Can, but does not change o1en] Rate of Change := Managed, Medium Digital Experience [Can and does change o1en] Rate of Change := Uncontrollable, Fast Data Subject Services [Does not change o1en] Rate of Change := Managed, Slow Digital Tradi@onal

47. 47 AR (Tarchitect to Marketect) CHITECT

48. 48 AR (Tarchitect to Marketect) CHITECT

49. Summary 49 build an architecture; -  API driven -  Consumer driven -  Minimalistic/utilized infrastructure -  Dynamic, act based on runtime events -  Iterative -  Platform for innovation and RAD using not loosing -  Existing applications and data -  SOA principles -  Middleware capabilities (integration engines and tools) -  Distributed deployment with functional containers

50. CONTACT US ! http://wso2.com

Add a comment

Related pages

A Pragmatic Approach to Microservice Architecture: The ...

... friendly pragmatic approach for MSA Essential middleware capabilities required ... middleware and cloud ... Architecture, Engineering and ...
Read more

A Pragmatic Approach to Microservice Architecture: The ...

A Pragmatic Approach to Microservice Architecture: The Role of Middleware . To view recording of this webinar please use the below URL: ...
Read more

Pragmatic Approach to Microservice Architecture - Role of ...

Pragmatic Approach to Microservice Architecture - Role ... Building a micro-services architecture ... Understanding Microservice Architecture ...
Read more

Scope Versus Size: a Pragmatic Approach to Microservice ...

... a Pragmatic Approach to Microservice ... Approach to Microservice Architecture: The Role of Middleware. [1] http://martinfowler ...
Read more

New WSO2 White Paper Examines a Pragmatic Approach ... - PRWeb

... outer architecture and how to leverage middleware in ... Pragmatic Approach to Microservice ... architecture at WSO2. In his role, ...
Read more

to Microservice Architecture - cdn.wso2.com

... a Pragmatic Approach to Microservice Architecture ... the outer architecture is about additional middleware ... play a vital role to accommodate ...
Read more

WSO2 to Present a Pragmatic Approach to Microservice ...

WSO2 to Present a Pragmatic Approach to Microservice ... (PRWEB) December 01, 2015. Microservice ... Microservice Architecture: Role of Middleware ...
Read more

WSO2 to Present Webinar Series on How to Leverage ...

Its iterative architectural approach and ... A Pragmatic Approach to Microservice Architecture: The Role of Middleware By using the correct middleware ...
Read more

New WSO2 White Paper Examines a Pragmatic Approach to ...

Paper discusses the core concepts of an MSA’s inner and outer architecture and how to leverage middleware in implementing a microservice architecture ...
Read more