10 Tips for failing at microservices

@koenighotze#Voxxed #10TipsMicroservices
10 Tips for failing badly at
Microservices
David Schmitz
Senacor Technologies

#VoxxedVienna #10TipsMicroservices @koenighotze
David Schmitz / @koenighotze
Senacor Technologies
Principal Architect
Programmer
That’s me coding EJBs

Disclaimer
This is not YOU!
Opinions are my OWN!TM

What’s in it for you?
Your boss want’s to modernise, but you don’t
Things to do to sabotage your project
Lessons learned the hard way
Things have been anonymised to protect the guilty

The Boss read about
microservices?

Extreme agile
cloud native digital
microservices!
Disrupt or be
disrupted!
Sounds good. And
cloud and agile equal
good?!?
Industry 4.0!
FTW!

“IT People! Make it happen! Build
me some microservices”

What the hell is a microservice and why should I care?

Microservices IMHO
Single Bounded Context
UI and Services
Independent
Self-Contained
Local storage
Share nothing
User Interface
Services
Persistence
Operations

Whatever! BLAH BLAH
User Interface
Services
Persistence
Operations
Too lazy to actually read all
this stuff…looks boring and I
want to look at funny cat
pics.

Sabotage Extravaganza
Follow these

Sabotage Extravaganza
10
9
8
7
6
5
4
3
2
1
Direction of
Awesomeness

10 - Go Full-Scale-Polyglot

Waldo-Tech Stack

Technical knowledge - Excitement
Groundhog Code - Redevelop solutions
Maintenance field trips
Heisenberg monitoring & Ops
The Zoo of Technology

Jump the Bandwagon
$ npm ls | grep @0
ui-demo@0.1.0
│ ├─┬ fbjs@0.8.8
│ │ │ ├─┬ encoding@0.1.12
│ │ │ │ └── iconv-lite@0.4.15
│ │ └── ua-parser-js@0.7.12
├─┬ react-scripts@0.8.5
│ │ ├── normalize-range@0.1.2
│ │ │ │ └── json5@0.5.1
│ │ │ └── source-map-support@0.4.11
│ │ │ └── regenerator-runtime@0.10.1
│ │ │ └── ms@0.7.2

Polyglot?

Polyglot?
thx @Codepitbull

Freedom is a human right
Everybody loves a puzzle - REST, HAL, SIREN
Find new friends while searching for fixes on
Stackoverflow
Synergies: Polyglot UI with beta status
Keep ops on their toes by multi-monitoring and
logging (easy win -> Date format!)

And ignore Ops!

9 - The data monolith
(c) Disney Corporation

Mum said we should share
Credit Account Payment
Giant SQL
Datastore

Mum said we should share

Name must be
VARCHAR(200) instead of
VARCHAR(50)

Account table changes

Boom

Sharing is a Good ThingTM
All microservices must share the database
Avoid table or schema ownership
Insidious dependencies, e.g. Connection pools
keep everybody awake at night

8 - The event monolith

Marketing Pitch
Customer
Homeaddress
Updated
Credit
acquired
New
Customer
Created
…
Direction of Time
Customer Credit
Event Store

Eventsourcing Marketing Pitch
Audit trail - Immutable history for free
Distributed data management
Decoupled microservices with CQRS
…and much more!

‘Das schöne
Österreich’ will no longer be
accepted as a country code

WET is the new DRY
Country:
“AU”
Country:
“Das schöne
Österreich”
…
Direction of Time
Customer Credit
Event Store

Don’t change messy past events
Don’t come up with a data strategy
Copy and Paste compensation actions
Event history as bugfixes
Dont’t need it? Play the “We might become
google or linkedin!” card

7 - The Home Grown monolith

– Carl Sagan (slightly paraphrased)
“If you wish to make MICROSERVICES from
scratch, you must first create a FRAMEWORK”
Wrapping up

Home made Eventsourcing
{
"type": "NewCustomerCreated",
"id": 1234,
"payload": {
}
}
{
"id": 1234,
"payload": {
}
}
CustomerAccount Reporting
ES V1 ES V1 ES V1

The customer system needs
special, non-numeric ids

Version increase
Customer V2
{
"id": "1234-5678",
"payload": {
...
}
}
ES 2

Runtime surprise
Customer V2Account Reporting
ES V1 ES V1ES 2
{
"id": "1234-5678",
"payload": {
...
}
}

Change the world event
Customer V2Account V2 Reporting V2
ES V2 ES V2ES 2

Microservice Promise
Customer
Account
Reporting
Independent release

Monolithic Release Plan
Customer
Account
Reporting
Common Release

Cross-cutting dependencies as social tools
Job insurance via invasive frameworks
Building frameworks is fun! Try it!
Ideas: Collections, String-Utils, Logging, ORM!

6 - Think of the meat cloud

W K
P T
Optimise your Revenue!

Who KNOWS how
to do it?K
P T
Optimise your Revenue!
Who WANTS it
to be done?
Who has the
required
PRIVILEGES?
Who has TIME
to actually
do it?

Insight: CD is very useful
Delivery
pipeline
Production

And the rest of the world?
Delivery pipeline
Production
…
Handcrafted
with love
Soulless
automation

W
Quickly…release a new
Customer microservice
K
P T

P T
KW

Ops Toolchain - Vi all the way!
P T
W K
P T

Prod Status - Illustration

Infrastructure is expensive…be proud to take
care of it
Microsoft Word is some kind of automation
Play the “we are not google” card
If someone asks, say you are using Docker

5 - The distributed monolith

Friends stay close together
Customer AccountCredit
Security

Let’s offer a discount to
new users

The Musketeer Pattern
Customer AccountCredit
Security

Combine the complexity of a
microservice architecture with
the rigidity and fragility of a
monolith

The network is reliable
Dependencies indicate good design, like in
Dependency Injection
Synchronous dependencies are easy
What is half a system good for, anyway? So
avoid Circuit breakers

4 - The SPA monolith

Micro is REST only
Customer REST Credit RESTAccount REST
Giant Monster UI

Add a mandatory
social-number field to the
customer

But not that mandatory. E.g. if
the customer is not committed, yet

No clear responsibility
Customer Domain Credit DomainAccount Domain
Comprehensive UI Domain
Model

Domain is spread around
Customer REST Credit RESTAccount REST

Ach, just put it there
Room
available

Meet people while discussion ownership
and conflicting features
Keep the testers busy with side effects
Single point of failure -> Easy to find

By all means, avoid composition
CreditCustomer Account
Tailor.JS / Project Mosaic

…and avoid Hyperlinks!
CreditCustomer Account

3 - The decision monolith

“But we need Java 7…it is 2017 after all!”

The sieve of sanity
Architecture & Design
Sieve

The sieve of sanity
Agile
Rx
Microservice
Actors Augmented realityCloud
AWS
WebRTC IoT
Blockchain

The sieve of sanity
Agile
Rx
Microservice
AWS
WebRTC IoT
Blockchain
Sieve

The sieve of sanity
JEE
WebSphere
Agile
Rx
Microservice
AWS
WebRTC IoT
Blockchain
Sieve

…works on larger scale, too
Sieve
Customer AccountCredit Security

Frustrate your coworkers
Irritate motivated colleagues
If you are older than 30…play the “This is
_real_ enterprise, kid” card
Ivory towers are beautiful
Assume people are dumb, and you are smart

2
The monolithic
business

MS is for Devs only
… … …
Branch Office Toolset Something

Let’s force the user to
always enter a valid address

No, the customer
should be able to enter partial
addresses

Requirements Ping Pong
Branch Office Toolset
Something
?????

Change Management

Requirements Management

Waterfall!!!11!!!

Slow means more time for Twitter!
The servant of many kings is a free man
Change / Requirement Mgmt. are your allies
Business people don’t know Eric Evans
Conway’s law works both ways

1 - Use a HR driven Architecture

It is easier to search for React
developers than for general
craftswomen

Frontend
Development
Service
Development
DevOps Team
Test
Business

Magic Specification
Success Template

Frontend Microservice
Service Microservice
Persistence
Microservice

Frontend Microservice
Service Microservice
Persistence
Microservice
Shared
stability
Shared
release
Convoluted
domains

Programmers do not like other people
Avoid spread of knowledge
Business knows the domain. Devs know tech
Nobody should have a big picture, keep them in the
dark
Meetings mean coffee and biscuits

And: In case of bugs…
It’s always the other team’s fault!
And: In case of bugs…
It’s always the other team’s fault!

Wrapping up….

The key to failure is the
hidden monolith

The hidden monolith
Data
Frontend
Framework
Deployment and Release
Process

Summary
MS mean Work - Fight them
Greenfield != Brownfield - The perfect excuse
Think of the organisational impact. You do not want to change!
Embrace the monolith
Microservices are a fad. Wait for SOAP 4.0
Dont’t underestimate the power of broken windows

Thank you!
Questions?
Thank you!

BACKUP

10 Tips for failing at microservices

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (20)

Similar to 10 Tips for failing at microservices

Similar to 10 Tips for failing at microservices (20)

More from David Schmitz

More from David Schmitz (6)

Recently uploaded

Recently uploaded (20)

10 Tips for failing at microservices