Slide 1

Slide 1 text

Microservices: Spring Netflix stack

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Change one thing, Change everything. Such minor changes, Such huge consequences.

Slide 7

Slide 7 text

P rovi si oni ng new i nstances for scal i ng takes ages. Heavy l oad i n one com ponent requi res everythi ng to scal e up.

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

µS customer µS user µS loyalty Config Server

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

Service Registry loyalty user billing billing’ loyalty user user origin Origin 1 Origin 2 billing loyalty origin

Slide 19

Slide 19 text

Service Registry loyalty user billing billing’ loyalty user billing user origin Origin 1 Origin 2 loyalty origin

Slide 20

Slide 20 text

billing Service Registry loyalty billing billing’ loyalty user user origin loyalty origin Origin 1 user billing’ billing Origin 2

Slide 21

Slide 21 text

Service Registry loyalty user user origin loyalty origin Origin 1 billing Origin 2 Service Registry loyalty user user origin loyalty origin Origin 1 billing Origin 2 loyalty Cached Registry

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Gateway µS µS µS µS µS µS

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

“API Gateways are fast becoming the Enterprise Service Bus of the microservices era” Sam Newman

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

Backend µS

Slide 39

Slide 39 text

Backend µS

Slide 40

Slide 40 text

µS stream information Backend

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

ZUUL EUREKA µS CONFIG µS µS HYSTRIX DASHBOARD TURBINE SPRING BOOT ADMIN MICROSERVICES DASHBOARD SPINNAKER

Slide 63

Slide 63 text

6

Slide 64

Slide 64 text

Is this any different from SOA?

Slide 65

Slide 65 text

Service Oriented Architecture? Yes, it’s SOA … but different implementation approach: Classic SOA integrates different applications as a set of services Microservices architect a single application as a set of services

Slide 66

Slide 66 text

Classic SOA integrates different applications as a set of services Enterprise Service Bus WS* WS* WS* WS* WS* WS* WS* WS* WS* WS* Workflow Engine Intelligence Orchestration

Slide 67

Slide 67 text

business platform accounting service contract service ordering service logistics service prospects service capability X service capability Y service external integrations backends { API } { API } { API } { API } { API } { API } { API } { API } { API } { API } { API } Microservices architect a single application as a set of services

Slide 68

Slide 68 text

Classic SOA integrates different applications as a set of services Typical implementation solution differs! Heavy-weight ESB WS*/SOAP Orchestration License-driven Target problem: Integrate (Legacy) Software Intelligent Communication Layer Light-weight HTTP/REST/JSON Choreography Target problem: Architect new Business Platform Dumb Communication Layer Intelligent Services Microservices architect a single application as a set of services

Slide 69

Slide 69 text

Thanks for listening! @andreasevers