Microservice Architecture (MSA) is emerging as a popular architecture pattern in today’s agile enterprise. Its iterative architecture and development methodologies are particularly attracting the interest of architects who need continuous delivery to fulfil business needs. But, is every characteristics of MSA new or even pragmatic? Asanka Abeysinghe, vice president of solutions architecture at WSO2, will provide insights into MSA requirements from real-world examples and provide details of an architect friendly pragmatic approach for this architecture pattern. Middleware plays a key role in successful MSA-based implementations. Using the correct middleware capabilities enable enterprises to fully leverage advantages provided by MSA, and ensures ease of implementation and faster time to market. Asanka will explain essential middleware capabilities required to resolve the MSA puzzle, where you can also utilize supportive technologies such as Continuous Integration (CI), containerization and Container as a Service (CaaS).

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

2. Enterprise today
2

3. In the process of moving to..
3

4. 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
4

5. Platform 3.0 : evolution of middleware
5
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

6. Microservices : our generation
6
Picture credit ; flicker

7. Microservices : new generation
7
Picture credit ; flicker

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

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

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

11. 11
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

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

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

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

15. MSA : reference architecture
15
Source : Gartner

16. MSA : characteristics
16
- 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

17. Componentize as services
17

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

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

20. 20
Source : connected company – Dave Gray

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

22. Platform for digital transformation
22

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

24. 24
Provide end-to-end middleware
capabilities.

25. 25

26. Smart endpoints and dumb pipes
26

27. But it leads to …....
27

28. 28
Support bus/broker architecture.

29. EIP (enterprise integration patterns)
29

30. MSA : extended with bus/broker
30

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

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

33. 33

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

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

36. Infrastructure automation
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. 38
Automated testing
Continuous integration
Support for containerization
Support for devops automation
Support for distributed deployment
Lean, independent runtime

39. Design for failure
39

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

41. Evolutionary design
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. 43
Pluggable, extensible
middleware architecture.

44. Phase layered strategy : platform
44
New
Ideas
Better
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
competitors.
I know what I want and
it doesn’t have to be
unique.
Systemsof Innovation
Differentiation
Record
Platform
Business Domain Services
[Can, but does not change often]
Rate of Change := Managed, Medium
Digital Experience
[Can and does change often]
Rate of Change := Uncontrollable, Fast
Data Subject Services
[Does not change often]
Rate of Change := Managed, Slow
Digital
Traditional

45. Summary
45
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

46. 46
AR (Tarchitect to Marketect) CHITECT

47. 47
AR (Tarchitect to Marketect) CHITECT

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