Microservices. treatment. and Modularity. or the difference between. and cure. Milen MARCH 17, 2015

Transcription

1 Microservices and Modularity or the difference between treatment and cure Milen MARCH 17, 2015

2 ~$ pidof java

3 ~$ pidof java ~$

4 ~$ pidof java ~$ ps aux grep java grep -v grep awk '{print $2}'

5 ~$ pidof java ~$ ps aux grep java grep -v grep awk '{print $2}' ~$

6 Monolith ~$ pidof java ~$ ps aux grep java grep -v grep awk '{print $2}' ~$ Microservices

7 What are Microservices

8 Microservices characteristics! 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

9 50% not strictly software but rather operations related! 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

10 Why consider Microservices

11 Reducing the complexity of Monoliths wrong but common answer

12

13 ...

14 ...

15 ...

16 or...

17 ... or...

18 or...

19 Reduced complexity!!! or...

20 ... then all you are doing is shifting complexity from inside a component to the connections between components.... it moves it to a place that's less explicit and harder to control.

21 What's cool about Microservices

22 The real power... is the ability for a developer to develop a single entity and then deploy that component multiple times Highly Scalable, Robust, Architecture In very straightforward terms... is a component model for building portable, reusable and scalable business components... for distributed environment.

23 Quotes from articles about EJB ( ) The real power... is the ability for a developer to develop a single entity and then deploy that component multiple times Highly Scalable, Robust, Architecture In very straightforward terms... is a component model for building portable, reusable and scalable business components... for distributed environment.

24 ... Companies worldwide have overspent about $1 billion... vendors are encouraging customer to buy high-end technology that they don't need.

25 Who is doing Microservices

26 microservices

27 microservices What do they have in common?

28 microservices They build microservices for their own needs!

29 microservices They build microservices for their own needs! This makes it easer for them to grow the DevOps culture hire the right people accept Decentralized approach automate infrastructure

30 ... a technique that is more effective for a more skillful team isn't necessarily going to work for less skillful teams... A poor team will always create a poor system...

31 Should I do Microservices

32 microservices Does your organization fit into that space?

33 ... you shouldn't start with a microservices architecture. Instead begin with a monolith, keep it modular, and split it into microservices once the monolith becomes a problem....

34 What else, if not Microservices

35 Microservices do not cure complexity! Actually nothing does!

36 The term "cure " means that, after medical treatment, the patient no longer has that particular condition anymore. Some diseases have no cure. The patient will always have the condition, but treatment can help to manage it.

37 Good treatment for complexity is enforcing clean modular architecture

38 ... The Deployment Model is a Detail.... there is no such thing as a micro-service architecture. Micro-services are a deployment option...

39 Interesting!?! But in my project it's not possible because of... Really?!? Modularizing Duke's forest JEE tutorial demo!

40 Glassfish Sh g in p i p EJB Pay A, F P J JS men E JB Model JPA Store JPA, EJB JSF t

41 EJB controllers JEE container OSGi services OSGi runtime Catalog usecase P di ort sp le la t y us mm ec e as r c e e co ity nt se e a Id ec s u A JP nce s te rsi In me pe r s mo r y ist en ce E- pe SpringBoot Database Domain Model F JS lay p dis Liferay

42 EJB controllers JEE container OSGi services OSGi runtime Catalog usecase P di ort sp le la t y us mm ec e as r c e e co ity nt se e a Id ec s u A JP nce s te rsi In me pe r s mo r y ist en ce E- pe SpringBoot Database Domain Model F JS lay p dis Liferay

43 EJB controllers JEE container OSGi services OSGi runtime Catalog usecase P di ort sp le la t y us mm ec e as r c e e co ity nt se e a Id ec s u A JP nce s te rsi In me pe r s mo r y ist en ce E- pe SpringBoot Database Domain Model F JS lay p dis Liferay

44 EJB controllers JEE container OSGi services OSGi runtime Catalog usecase P di ort sp le la t y us mm ec e as r c e e co ity nt se e a Id ec s u A JP nce s te rsi In me pe r s mo r y ist en ce E- pe SpringBoot Database Domain Model F JS lay p dis Liferay

45 EJB controllers JEE container OSGi services OSGi runtime Catalog usecase P di ort sp le la t y us mm ec e as r c e e co ity nt se e a Id ec s u A JP nce s te rsi In me pe r s mo r y ist en ce E- pe SpringBoot Database Domain Model F JS lay p dis Liferay

46

47 Modularity Is a important software architecture concept! One can design modular application without Microservices

48 The OSGi specification describes a modular system and a service platform for the Java programming language The architecture of choice for Confluence Eclipse Fuse ESB Glassfish Jboss JIRA and JonAS Service Mix Weblogic Websphere...

49 Same characteristics but more flexible! 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

50 This is not theory! We do this at We are transforming a huge code base into small simple core and OSGi (micro)services! We have so far extracted over 80 apps and we are not done yet!

51 @LiferayPL