Microservices: 5 Years In

Welcome!
Midsummer Vancouver
Microservices Meetup
July 31, 2019
Brought to you by:

Agenda
 Microservices: 5 Years In, Matt McLarty,
MuleSoft (a Salesforce Company)
 Microservices: What to Expect, Alexei
Potiagalov, SAP
 Unconference Discussions

Microservices: 5 Years In
Matt McLarty
Global Leader, API Strategy
MuleSoft, a Salesforce Company
@mattmclartybc

Microservices Origins
Microservice
ArchitectureAgile
DevOps
Cloud
SOA
APIs

Microservices – The Bliki Post
https://martinfowler.com/articles/microservices.html

Microservice Architecture Characteristics
Componentization
via Services
Organized around
Business
Capabilities
Products not
Projects
Smart endpoints
and dumb pipes
Decentralized
Governance
Decentralized Data
Management
Infrastructure
Automation
Design for Failure
Evolutionary
Design

Componentization via Services
2014
 Services vs. Libraries
 Network/process
boundaries
 Explicit interfaces
 Independent deployability
“A service may consist of multiple
processes that will always be
developed and deployed together”
2019
 Kubernetes pods
 Inner service boundaries
(Lambda, legacy adapters)
 Aggregated interfaces
(GraphQL)
 Monorepo debate

Organized around Business Capabilities
2014
 Business vs. tech function
 Cross-functional teams
 Teams aligned to contexts
 One-to-many contexts to
services
 Service size tied to team
size
2019
 DDD resurgence
 Spotify model
 Size debate
 Enterprise struggles
– Business vs. IT split
– Complex business domains
– Cross-reference contexts

Products not Projects
2014
 Long term ownership
 “You build it, you run it”
 Ongoing user focus
 Essence of Agile
2019
 APIs as products
– Product design thinking
 Agile increasingly the norm
 Enterprise struggles
– SAFe vs. Agile principles
– Regulatory constraints
– Budget cycles

Smart endpoints and dumb pipes
2014
 Complex logic inside
service boundaries
 “Be of the web, not behind
the web”
 HTTP APIs, lightweight
messaging
 Anti-ESB
2019
 Data vs. control plane
– Control plane warrants “pipe
intelligence”
– Security, routing, observability
 Service mesh obsession
 Service proxy vs. API
gateway

Decentralized Governance
2014
 Avoid “one size fits all”
 Right tool for the job
 Battle-tested standards for
interop concerns
 In-house open source
 Evolving contracts
 Make it easy to do right
2019
 Focus on incentive-based
governance
 OpenAPI, GraphQL, gRPC
 Still plenty of top down,
one size fits all thinking
 Rapidly evolving technology
landscape, not battle-tested
(service mesh in particular)

Decentralized Data Management
2014
 Split by bounded contexts
 Polyglot persistence
 Transactionless
 Eventual consistency
 Compensating business
processes
2019
 Layers of data partitioning
– e.g. Separate schemas, shared
DB
 Saga pattern
 Event-based choreography
 One of the harder
characteristics to get right

Infrastructure Automation
2014
 Cloud tech
 Continuous delivery
 Test automation
 Automated deployment
 Automated monitoring,
recovery and scaling
2019
 DevOps a parallel trend to
microservices
 Increasing use of
deployment pipelines
 More cloud agility in use
 Test automation the biggest
remaining obstacle

Design for failure
2014
 Resilience
 Expect failures
 MTTR vs. MTBF
 Semantic monitoring
 Circuit breaker, bulkhead,
timeouts
 Synch vs. asynch call chains
2019
 Overhead of library-based
resilience code
 Service mesh and API
gateways offload handling
 Accelerate book validates
importance of resilience
 Platform layers increase
failure permutations

Evolutionary Design
2014
 Optimize change over time
 Frequent, fast, well-
controlled changes
 Design for replacement
 Coexistence with monoliths
 Keep things together that
change together
 Minimize versioning
2019
 Too much emphasis on
initial microservices build
 Too many “big bets”
 Accelerate book validates
value of change frequency
 “Bimodal IT”
 Enterprises struggle to
deprecate services

Missing?
 Not much!
 Security
 Cross-system capabilities
 Cross-organization responsibilities
 Front ends
 Resource guide: https://martinfowler.com/microservices/

In summary…
 Core characteristics of the Fowler/Lewis post still apply
 Microservices movement evolved in parallel with Agile and
DevOps especially
 Some of been explored in depth and revealed new complexity
– Especially tech-focused areas
 Some have been overlooked or deemphasized
– Design and organizational factors
 The services are the point!

Microservices: 5 Years In

More Related Content

What's hot (20)

Similar to Microservices: 5 Years In (20)

Recently uploaded (20)

Microservices: 5 Years In