Microservices: Spring Netflix stack

In this new world speed wins. Organisations can no longer afford ignoring agility in IT, and getting to production faster becomes a competitive advantage.

Delivering smaller batches in a faster way has been central to the Agile methodology being adopted in many companies, but one can only go as fast as the architecture allows. When we really want to achieve speed in delivering, the architecture has to match the methodology.

Smaller batches of independent work reflects through microservices, an architectural style which isolates functionality into bounded contexts, independently deployable with clear boundaries.

But as always, any architecture has downsides which need to be addressed. Luckily high performing organisations such as Netflix have released open source components to deal with this complexity. Join this talk to learn about what microservices are all about, and how it can help your organisation buckle up and outperform its competitors.

Transcript

1. Microservices: Spring Netflix stack
6. Change one thing, Change everything. Such minor changes, Such huge consequences.
7. 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.
14. µS customer µS user µS loyalty Config Server
18. Service Registry loyalty user billing billing’ loyalty user user origin Origin 1 Origin 2 billing loyalty origin
19. Service Registry loyalty user billing billing’ loyalty user billing user origin Origin 1 Origin 2 loyalty origin
20. billing Service Registry loyalty billing billing’ loyalty user user origin loyalty origin Origin 1 user billing’ billing Origin 2
21. 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
25. Gateway µS µS µS µS µS µS
32. “API Gateways are fast becoming the Enterprise Service Bus of the microservices era” Sam Newman
38. Backend µS
39. Backend µS
40. µS stream information Backend
62. ZUUL EUREKA µS CONFIG µS µS HYSTRIX DASHBOARD TURBINE SPRING BOOT ADMIN MICROSERVICES DASHBOARD SPINNAKER
64. Is this any different from SOA?
65. 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
66. 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
67. 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
68. 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
69. Thanks for listening! @andreasevers