Delivering with Microservices - How to Iterate Towards Sophistication

DELIVERING WITH
MICROSERVICES
HOW TO ITERATE TOWARDS SOPHISTICATION

FROM THE TRENCHES
LESSONS LEARNED

FROM THE TRENCHES
NANO SERVICES

CROSS CUTTING CONCERNS
public void RefreshAllResults()
{
[…]
WithConnection(
connection =>
connection.Execute(DbTable + "UpdateAll", CommandType.StoredProcedure));
[…]
}
results-service
UpdateAllResults
service-a service-b service-c
FROM THE TRENCHES

REFLECTIONS
microservices?
FROM THE TRENCHES

REFLECTIONS
microservices? need big upfront design?
FROM THE TRENCHES

DEFINE MICROSERVICES
WHEN AGILE MEETS DISTRIBUTED SYSTEMS

AN ALTERNATIVE TO VENDOR-LED SOA
http://www.infoq.com/presentations/webber-guerilla-soa

The
Problem

The
Problem
The
Solution

The
Problem
The
Solution
The
Problem
Again

The
Problem
The
Solution
Back to
The
Future
The
Problem
Again

DISTRIBUTED AND WEB ARCHITECTURES
C++
1980s
Java
1990s
ANSI C
TCP Client-Sever
RPC
CORBA
RMI

DISTRIBUTED AND WEB ARCHITECTURES
C++
1980s
Java
1990s
ANSI C
TCP Client-Sever
RPC
CORBA
RMI
2000s 2010s
XML JavaScript
SOAP
SOA
JSON
REST
HTTP
The Internet

SOFTWARE DEVELOPMENT METHODOLOGIES
RUP
XP
Continuous
Integration
Agile
Continuous
Delivery
1980s 1990s 2000s 2010s

THE PRODIGAL SON
Service
Oriented
Architecture
Continuous
Delivery
Microservices
XP AgileThe Internet
Distributed
Systems

REFLECTIONS
Microservices

MICROSERVICES RUSH
WHAT MAKE THEM SO POPULAR?

INTEREST
0
January 2014
June 2015
100
Google Trends Data
# “microservices” searches
MICROSERVICES RUSH

SCALE
"In order to scale to the next order of magnitude, we're
rethinking the fundamentals of our architecture"
Philip Fisher-Ogden, Director of Engineering
"We created the viewing service to encapsulate the domain of
viewing data collection, processing, and providing "
"These components would be easier to develop, test, debug,
deploy, and operate if they were extracted into their own services."
http://www.techrepublic.com/article/netﬂix-on-how-to-build-services-that-scale-beyond-millions-of-users/
MICROSERVICES RUSH

BREAK THE MONOLITH
Monolithic Perl —> Monolithic C++ —> Java —> microservices
Monolithic C++ —> Perl / C++ —> Java / Scala -> microservices
Monolithic Rails —> JS / Rails / Scala —> microservices
MICROSERVICES RUSH

BUSINESS VALUE FIRST
https://yow.eventer.com/yow-2011-1004/domain-driven-design-strategies-for-dealing-with-legacy-systems-by-eric-evans-1033
MICROSERVICES RUSH

CONWAY’S LAW
"Any organisation that designs a system […] will
inevitably produce a design whose structure is a copy
of the organisation's communication structure."
Melvin Conway, How Do Committees Invent - 1968
MICROSERVICES RUSH

REFLECTIONS
Microservices
MICROSERVICES RUSH

REFLECTIONS
Microservices
strategic value
MICROSERVICES RUSH

REFLECTIONS
Microservices
strategic value break the monolith
MICROSERVICES RUSH

REFLECTIONS
Microservices
strategic value break the monolith scale
MICROSERVICES RUSH

REFLECTIONS
Microservices
strategic value break the monolith scale re-org
MICROSERVICES RUSH

DELIVERING MICROSERVICES
IN AN AGILE WAY

THE PROBLEM
Infrastructure
Features
Infrastructure
Features
WatchlistService
Type of work delivered over time

THE GOAL

JOURNEY

JOURNEY
Discovery

JOURNEY
Discovery Release 1

JOURNEY
Discovery Release 1 Release 2

JOURNEY
Discovery Release 1 Release 2 Release N…

JOURNEY
Capabilities

DISCOVERY - WHY MICROSERVICES

BUSINESS & ARCHITECTURE CONTRACT

Strategic
Goals

Strategic
Goals
Architectural
Principles

Strategic
Goals
Architectural
Principles
Design & Delivery
Practices

USER JOURNEYS ACROSS SERVICES
users
journeys
services
journeys

RELEASE 1 - BUILD A MINILITH

RELEASE 1 - ARCHITECTURE

greenﬁeld

greenﬁeld
brownﬁeld
monolith

greenﬁeld
brownﬁeld
monolith
minilith
minilith

minilith
greenﬁeld
brownﬁeld
monolith
minilith
minilith

minilith
greenﬁeld
brownﬁeld
monolith
minilith
minilith
Client

minilith
greenﬁeld
brownﬁeld
monolith
minilith
minilith
Client
Presentation

minilith
greenﬁeld
brownﬁeld
monolith
minilith
minilith
Client
Presentation
Biz Services

minilith
greenﬁeld
brownﬁeld
monolith
minilith
minilith
Client
Presentation
Biz Services
services

RELEASE 1 - CONTINUOUS DELIVERY
• CODE
• BUILD
• PLAN
• RELEASE
• TO TEST FLIGHT
• CODE
• BUILD
• PLAN
• RELEASE
• TO TEST FLIGHT
CODE
PLAN
BUILD
TEST
RELEASE TO
PRODUCT OWNER
+ BETA
INSTALL
TRACK USAGE
USER
FEEDBACK
Continuous
Integration
Usability and
Feedback Cycle

RELEASE 1 - CONTRACT TESTING
Functional
Integration
Unit Unit
Contracts
Web Application Web Services

RELEASE 1 - COUPLING GRAPHS WITH D3JS

Requests Flow
http://techblog.netﬂix.com/2015/02/a-microscope-on-microservices.html

Dependencies
https://www.youtube.com/watch?v=hsoovFbpAoE
Requests Flow
http://techblog.netﬂix.com/2015/02/a-microscope-on-microservices.html

RELEASE 1 - TRANSACTIONS LOGGING
service-A service-B
service-C

service-A service-B
service-C
ID: ABCD

service-A service-B
service-C
ID: ABCD
ID: EFGH
caused by ABCD

service-A service-B
service-C
ID: ABCD
ID: EFGH
caused by ABCD
ID: IJKL
caused by EFGH

RELEASE 1 - DIFFERENT LEVELS OF MONITORING
Infrastructure
New Relic
RuntimeLog
Logstash & Kibana

RELEASE 1 - BUILD CAPABILITIES
• Continuously Deliver
CI, automated builds, tests, and deployments, release management
• Re-think the pyramid of tests
Favor contracts testing to UI functional testing
• Control dependencies
Modules integration via HTTP, dependency graph, transaction logging
• Release to production
Learn about your prod environment, consider containers and/or in-process
lightweight web servers, load balancers, caching, etc…
• Monitor & Analyse
Have system monitoring and data analytics in place.

RELEASE 2 - FIRST MICROSERVICES

greenﬁeld
brownﬁeld
monolith
services
services

greenﬁeld
brownﬁeld
monolith
Client
Presentation
services
services

greenﬁeld
brownﬁeld
monolith
Client
Presentation
Biz Services
services
services

greenﬁeld
brownﬁeld
monolith
Client
Presentation
Biz Services
services
services
services

RELEASE 2 - NEW SERVICE USE CASES

new bounded context

new bounded context scale separately

security

securitydata aggregation

RELEASE 2 - ISOLATION
DATA
"No direct database access is allowed from outside the
service, and there’s no data sharing among the services"
Werner Vogels, CTO and Vice President of amazon.com

CONTAINERS
LXD

INTEGRATION
Orchestration Choreography
http://www.thoughtworks.com/insights/blog/scaling-microservices-event-stream

RELEASE 2 - LOWER BARRIER TO ENTRY
TO BE ADDED

RELEASE 2 - BUILD WHAT YOU CAN SUPPORT

RELEASE 2 - UNDERSTAND SERVICES
• Know if and when to create a new service
new bounded context, aggregation, security, scale independently
• Deﬁne (your level of) isolation
code, compilation, runtime, persistence, integration
• Reduce barrier to entry
repository blueprint, pipeline template, scaﬀolding script
• Build what you can support
develop DevOps culture (e.g. infrastructure as code)

RELEASE N - SCALE

RELEASE N - SCALING FOR LOAD
CAP THEOREM
Availability
Consistency
Partition
Tolerance

ARCHITECTURE

ARCHITECTURE
Consistent & Available
(No Partition Tolerance)

ARCHITECTURE
Partition Tolerant & Available
(No consistency)

ARCHITECTURE
(No consistency)
(Eventual consistency)
read replicas
Writes Reads

RELEASE N - SCALING DELIVERY

PO
BA
QA
DEV
OPS
SERVICE TEAMS

PO
BA
QA
DEV
OPS
SERVICE TEAMS
service team

PO
BA
QA
DEV
OPS
SERVICE TEAMS
service team
service A
service B service C
HQ

PO
BA
QA
DEV
OPS
SERVICE TEAMS
service team
service A
service B service C
HQ
service A service B service C

DISTRIBUTED TEAMS
CHENGDUBRISBANE SYDNEY PERTH

DISTRIBUTED TEAMS
CHENGDUBRISBANE
mogul-service pizza-image-service
SYDNEY PERTH

DISTRIBUTED TEAMS
CHENGDUBRISBANE
mogul-service pizza-image-service
SYDNEY PERTH
media-serviceauth-service
dough-service
email-service
mogul-private-service
moderation-service
pizza-service
order-service
leaderboard-service
charity-service

Microservices
CONCLUSION
KEY TAKEAWAYS

Microservices
CONCLUSION
• what are microservices
KEY TAKEAWAYS

Microservices
CONCLUSION
• does not require big upfront design
KEY TAKEAWAYS

Microservices
CONCLUSION
• application of agile techniques to distributed systems
KEY TAKEAWAYS

Microservices
CONCLUSION
• agree with business why microservices
KEY TAKEAWAYS

Microservices
CONCLUSION
• continuous delivery, testing strategy, monitoring
KEY TAKEAWAYS

Microservices
CONCLUSION
• start small, grow your own capabilities
KEY TAKEAWAYS

Microservices
CONCLUSION
• scale your services and your organisation
KEY TAKEAWAYS

Microservices
CONCLUSION
• scale your services and your organisation
• choose what works for you
KEY TAKEAWAYS

jeandamore
blog.corsamore.com
jeandamore
jdamore
Jean D’Amore
Technology Market Principal
jdamore@thoughtworks.com
ABOUT ME

Delivering with Microservices - How to Iterate Towards Sophistication

More Related Content

What's hot

Viewers also liked

Similar to Delivering with Microservices - How to Iterate Towards Sophistication

More from Thoughtworks

Recently uploaded

Delivering with Microservices - How to Iterate Towards Sophistication