Microservices Meet Real-World Projects: Lessons Learned

Slide 1

Slide 1 text

MicroServices meet Real World projects Tammo van Lessen | [email protected] Alexander Heusingfeld | [email protected] #javaone #microservices www.innoQ.com

Slide 2

Slide 2 text

MicroServices meet Real World projects Tammo van Lessen | [email protected] Alexander Heusingfeld | [email protected] #javaone #microservices www.innoQ.com

Slide 3

Slide 3 text

Consultings gigs...

Slide 4

Slide 4 text

“We’d like to have a microservice architecture!”

Slide 5

Slide 5 text

When reviewing a monolithic application … © innoQ/Roman Stranghöner

Slide 6

Slide 6 text

…and taking a look into the black box… © innoQ/Roman Stranghöner

Slide 7

Slide 7 text

…you’ll likely find it consists of multiple Bounded Contexts. © innoQ/Roman Stranghöner

Slide 8

Slide 8 text

If you cut a monolithic system along its very domains …

Slide 9

Slide 9 text

… and wrap every domain in a separate, replaceable web application …

Slide 10

Slide 10 text

… then that application can be referred to as a self- contained system (SCS).

Slide 11

Slide 11 text

https://www.innoq.com/de/links/self-contained-systems-infodeck/ more information on self-contained systems (SCS) can be found at #javaone #microservices

Slide 12

Slide 12 text

Architectural Decisions

Slide 13

Slide 13 text

Architectural Decisions > Domain Architecture

Slide 14

Slide 14 text

Architectural Decisions > Domain Architecture > Macro Architecture

Slide 15

Slide 15 text

Architectural Decisions > Domain Architecture > Macro Architecture > Micro Architecture

Slide 16

Slide 16 text

Isn't there more than that…

Slide 17

Slide 17 text

At a project meeting…

Slide 18

Slide 18 text

Did you think about the people   who make your architecture exist?

Slide 19

Slide 19 text

us vs. them

Slide 20

Slide 20 text

“Don’t care about this, it’s our business!” “Alarming is our concern, don’t bother about it!” “No need for a discussion, we always fix that during deployment.” “That’s part of the handover to operations.”

Slide 21

Slide 21 text

overcome “us vs. them”

Slide 22

Slide 22 text

overcome “us vs. them” > cross-functional != cross-department

Slide 23

Slide 23 text

overcome “us vs. them” > cross-functional != cross-department > have one manager to decide on a team’s targets

Slide 24

Slide 24 text

overcome “us vs. them” > cross-functional != cross-department > have one manager to decide on a team’s targets > don’t neglect team-building

Slide 25

Slide 25 text

overcome “us vs. them” > cross-functional != cross-department > have one manager to decide on a team’s targets > don’t neglect team-building > trust is not optional

Slide 26

Slide 26 text

well-known pros are subjective

Slide 27

Slide 27 text

“Operating a monolith is easier!”

Slide 28

Slide 28 text

Of course it’s easier…

Slide 29

Slide 29 text

It’s always easier… …if the complexity is on someone else’s desk.

Slide 30

Slide 30 text

“Separating teams duplicates work!”

Slide 31

Slide 31 text

The manageable, domain specific scope enables the development, operation and maintenance of an SCS by a independent team. Team 1 Team 2 Team 3

Slide 32

Slide 32 text

share ideas share concepts don’t share libraries Team 1 Team 2 Team 3

Slide 33

Slide 33 text

“Operational costs are increased!”

Slide 34

Slide 34 text

Monolith

Slide 35

Slide 35 text

Microservices?

Slide 36

Slide 36 text

“Deployments cannot be faster,   we have an established process!”

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

What this taught us

Slide 41

Slide 41 text

What this taught us > enable fast feedback for your team

Slide 42

Slide 42 text

What this taught us > enable fast feedback for your team > automate what’s next to you first

Slide 43

Slide 43 text

What this taught us > enable fast feedback for your team > automate what’s next to you first > do your homework before you teach others

Slide 44

Slide 44 text

What this taught us > enable fast feedback for your team > automate what’s next to you first > do your homework before you teach others > other people will notice the benefits

Slide 45

Slide 45 text

What this taught us > enable fast feedback for your team > automate what’s next to you first > do your homework before you teach others > other people will notice the benefits > complex processes can be adopted, divide them and take one step at a time

Slide 46

Slide 46 text

“pets vs. cattle”

Slide 47

Slide 47 text

https://www.ﬂickr.com/photos/cornelii/531691572 https://www.ﬂickr.com/photos/cornelii/531691572

Slide 48

Slide 48 text

https://www.ﬂickr.com/photos/cornelii/531691572 https://www.ﬂickr.com/photos/cornelii/531691572

Slide 49

Slide 49 text

summarized: change perspectives!

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

http://izismile.com/2013/01/22/buyers_beware_its_a_matter_of_perspective_3_pics.html

Slide 53

Slide 53 text

A company which embraced and evolved

Slide 54

Slide 54 text

http://projectcartoon.com/cartoon/1

Slide 55

Slide 55 text

Modernisation Strategies

Slide 56

Slide 56 text

Big Bang

Slide 57

Slide 57 text

Change via Copy

Slide 58

Slide 58 text

Change via Extraction

Slide 59

Slide 59 text

Strangulate Bad Parts

Slide 60

Slide 60 text

http://aim42.org/ more information on software modernisation   can be found at #javaone #microservices

Slide 61

Slide 61 text

conclusion

Slide 62

Slide 62 text

Conway’s Law “Organizations which design systems are constrained to produce systems which are copies of the communication structures of these organizations.” – M.E. Conway Organization ˠ Architecture

Slide 63

Slide 63 text

Summary #javaone #microservices

Slide 64

Slide 64 text

Summary > distributed systems are hard - organizational impact, too #javaone #microservices

Slide 65

Slide 65 text

Summary > distributed systems are hard - organizational impact, too > don't forget: there's always at least one other perspective #javaone #microservices

Slide 66

Slide 66 text

Summary > distributed systems are hard - organizational impact, too > don't forget: there's always at least one other perspective > Don’t overwhelm people, change one thing at a time #javaone #microservices

Slide 67

Slide 67 text

Slide 68

Slide 68 text

Thank you! Questions? Comments? Tammo van Lessen | @taval [email protected] Alexander Heusingfeld | @goldstift [email protected] innoQ Deutschland GmbH Krischerstr. 100 40789 Monheim am Rhein Germany Phone: +49 2173 3366-0 innoQ Schweiz GmbH Gewerbestr. 11 CH-6330 Cham Switzerland Phone: +41 41 743 0116 www.innoq.com Ohlauer Straße 43 10999 Berlin Germany Ludwigstraße 180 E D-63067 Offenbach Germany Kreuzstr. 16 D-80331 München Germany https://www.innoq.com/en/talks/2015/10/ javaone-2015-microservices-projects-selfcontained-systems/ #javaone #microservices