microservices and modularity or the difference between treatment and cure!

51
MARCH 17, 2015 Microservices and Modularity or the difference between treatment and cure Milen Dyankov @milendyankov

Upload: milen-dyankov

Post on 16-Jul-2015

926 views

Category:

Software


1 download

TRANSCRIPT

Page 1: Microservices and Modularity or the difference between treatment and cure!

MARCH 17, 2015

Microservicesand

Modularityor

the difference between

treatmentand

cureMilen Dyankov@milendyankov

Page 2: Microservices and Modularity or the difference between treatment and cure!

~$ pidof java

Page 3: Microservices and Modularity or the difference between treatment and cure!

~$ pidof java9927 2151~$

Page 4: Microservices and Modularity or the difference between treatment and cure!

~$ pidof java9927 2151~$ ps aux | grep java | grep -v grep | awk '{print $2}'

Page 5: Microservices and Modularity or the difference between treatment and cure!

~$ pidof java9927 2151~$ ps aux | grep java | grep -v grep | awk '{print $2}'21519927~$

Page 6: Microservices and Modularity or the difference between treatment and cure!

~$ pidof java9927 2151~$ ps aux | grep java | grep -v grep | awk '{print $2}'21519927~$

Monolith

Microservices

Page 7: Microservices and Modularity or the difference between treatment and cure!

What are

Microservices

Page 8: Microservices and Modularity or the difference between treatment and cure!

Componentization via ServicesOrganized around Business CapabilitiesProducts not ProjectsSmart endpoints and dumb pipesDecentralized GovernanceDecentralized Data ManagementInfrastructure AutomationDesign for failureEvolutionary Design

Microservices characteristics!

Page 9: Microservices and Modularity or the difference between treatment and cure!

Componentization via ServicesOrganized around Business CapabilitiesProducts not ProjectsSmart endpoints and dumb pipesDecentralized GovernanceDecentralized Data ManagementInfrastructure AutomationDesign for failureEvolutionary Design

50% not strictly software butrather operations related!

Page 10: Microservices and Modularity or the difference between treatment and cure!

Why consider

Microservices

Page 11: Microservices and Modularity or the difference between treatment and cure!

wrong but common answer

Reducing the complexity of Monoliths

Page 12: Microservices and Modularity or the difference between treatment and cure!
Page 13: Microservices and Modularity or the difference between treatment and cure!

. . .

Page 14: Microservices and Modularity or the difference between treatment and cure!

. . .

Page 15: Microservices and Modularity or the difference between treatment and cure!

. . .

Page 16: Microservices and Modularity or the difference between treatment and cure!

. . .or

Page 17: Microservices and Modularity or the difference between treatment and cure!

. . .or

. . .∞

Page 18: Microservices and Modularity or the difference between treatment and cure!

. . .or

. . .∞

. . .

Page 19: Microservices and Modularity or the difference between treatment and cure!

. . .or

. . .

Reduced complexity !!!

. . .

Page 20: Microservices and Modularity or the difference between treatment and cure!

. . .

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.

Page 21: Microservices and Modularity or the difference between treatment and cure!

Microservices

What's cool about

Page 22: Microservices and Modularity or the difference between treatment and cure!

“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 forbuilding portable, reusable and scalable business

components ... for distributed environment.”

Page 23: Microservices and Modularity or the difference between treatment and cure!

“The real power ... is the ability for a developer to develop a single entity and then deploy that component multiple times”

www.onjava.com/pub/a/onjava/2001/12/19/eejbs.html

“Highly Scalable, Robust, Architecture” www.dhlee.info/computing/ejb/reference/seybold_ejb.pdf

“In very straightforward terms ... is a component model forbuilding portable, reusable and scalable business

components ... for distributed environment.”www.idt.mdh.se/kurser/ct3340/archives/ht08/papersRM08/37.pdf

Quotes from articles about EJB ( 1999 – 2002 )

Page 24: Microservices and Modularity or the difference between treatment and cure!

. . .

Companies worldwide have overspent about $1 billion

. . .

vendors are encouraging customer to buy

high-end technology that they don't need.

Page 25: Microservices and Modularity or the difference between treatment and cure!

Who is doing

Microservices

Page 26: Microservices and Modularity or the difference between treatment and cure!

microservices

Page 27: Microservices and Modularity or the difference between treatment and cure!

microservices

What do they have in common ?

Page 28: Microservices and Modularity or the difference between treatment and cure!

microservices

They buildmicroservices for

their own needs!

Page 29: Microservices and Modularity or the difference between treatment and cure!

microservices

They buildmicroservices for

their own needs!

This makes it easer for them to grow the DevOps culture hire the right people accept “Decentralized” approach automate infrastructure

Page 30: Microservices and Modularity or the difference between treatment and cure!

. . .

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

. . .

Page 31: Microservices and Modularity or the difference between treatment and cure!

Should I do

Microservices

Page 32: Microservices and Modularity or the difference between treatment and cure!

microservices

Does your organization fit into that space?

Page 33: Microservices and Modularity or the difference between treatment and cure!

. . .

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.

. . .

Page 34: Microservices and Modularity or the difference between treatment and cure!

Microservices

What else, if not

Page 35: Microservices and Modularity or the difference between treatment and cure!

Microservices do not

cure complexity!

Actually nothing does !

Page 36: Microservices and Modularity or the difference between treatment and cure!

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.

Page 37: Microservices and Modularity or the difference between treatment and cure!

Good treatment for complexity is enforcing

clean modular

architecture

Page 38: Microservices and Modularity or the difference between treatment and cure!

. . .

The Deployment Model is a Detail.. . .

there is no such thing as a micro-service

architecture.Micro-services are a

deployment option . . .

Page 39: Microservices and Modularity or the difference between treatment and cure!

Interesting !?!

But in my project it's not possible because of . . .

Really ?!?

Modularizing “Duke's forest”

JEE tutorial demo!

https://github.com/azzazzel/modular-dukes-forest

Page 40: Microservices and Modularity or the difference between treatment and cure!

ModelJPA

StoreJPA, EJB

JSF

Shipping

JPA, EJB

JSF

Payment EJB

Glassfish

Page 41: Microservices and Modularity or the difference between treatment and cure!

DomainModel

Catalogusecase

Identity

usecase E-com

merc

e

usecaseJ

PA

pe

rsistence

In-memorypersistence

EJBcontrollers

OSGiservices

Portle

tdis

play

JSF

display

JEEcontainer

SpringBoot

OSGiruntime

Liferay

Database

Page 42: Microservices and Modularity or the difference between treatment and cure!

DomainModel

Catalogusecase

Identity

usecase E-com

merc

e

usecaseJ

PA

pe

rsistence

In-memorypersistence

EJBcontrollers

OSGiservices

Portle

tdis

play

JSF

display

JEEcontainer

SpringBoot

OSGiruntime

Liferay

Database

Page 43: Microservices and Modularity or the difference between treatment and cure!

DomainModel

Catalogusecase

Identity

usecase E-com

merc

e

usecaseJ

PA

pe

rsistence

In-memorypersistence

EJBcontrollers

OSGiservices

Portle

tdis

play

JSF

display

JEEcontainer

SpringBoot

OSGiruntime

Liferay

Database

Page 44: Microservices and Modularity or the difference between treatment and cure!

DomainModel

Catalogusecase

Identity

usecase E-com

merc

e

usecaseJ

PA

pe

rsistence

In-memorypersistence

EJBcontrollers

OSGiservices

Portle

tdis

play

JSF

display

JEEcontainer

SpringBoot

OSGiruntime

Liferay

Database

Page 45: Microservices and Modularity or the difference between treatment and cure!

DomainModel

Catalogusecase

Identity

usecase E-com

merc

e

usecaseJ

PA

pe

rsistence

In-memorypersistence

EJBcontrollers

OSGiservices

Portle

tdis

play

JSF

display

JEEcontainer

SpringBoot

OSGiruntime

Liferay

Database

Page 46: Microservices and Modularity or the difference between treatment and cure!

http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html

Page 47: Microservices and Modularity or the difference between treatment and cure!

Microservices

ModularityIs a important software architecture concept!

One can design modular application without

Page 48: Microservices and Modularity or the difference between treatment and cure!

The OSGi specification describes a modular system and a service platform for the

Java programming language

ConfluenceEclipse

Fuse ESB Glassfish

JbossJIRA

JonASService Mix

WeblogicWebsphere

. . .

The architecture of choice for

and

Page 49: Microservices and Modularity or the difference between treatment and cure!

Componentization via ServicesOrganized around Business CapabilitiesProducts not ProjectsSmart endpoints and dumb pipesDecentralized GovernanceDecentralized Data ManagementInfrastructure AutomationDesign for failureEvolutionary Design

Same characteristics but more flexible !

Page 50: Microservices and Modularity or the difference between treatment and cure!

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!

This is not theory! We do this at

Page 51: Microservices and Modularity or the difference between treatment and cure!

[email protected]

http://www.liferay.com/web/milen.dyankov/

@milendyankov@LiferayPL

http://www.liferay.com

@Liferay

http://www.facebook.com/Liferay