2017

You might not need Microservices

2017

Who Am I ?

Jean-Christophe Bohin - Inovia

2017

“There’s a new project, let’s do it in microservices”

- Client (or team member. Or any Hipster. Whatever)

2017

“Alert: you don’t want that.No you don’t. Stop it. Right now.

Not under my watch!”- Me.Every. Single. Time.

2017

Why would you want microservices ?

If It's “hype”, if you “think” you need it, or

if you “want” it...

...then you are doing it wrong.

2017

Spoiler alert: Microservices are an interesting

pattern, but not a magic bullet.If you do things wrong it won't be

good. Microservices or not.

2017

Be ready to face…

2017

Performance problems

2017

Huge formalisation and communication needs

2017

Distributed systems headaches

2017

Polyglotism fallacy

2017

Massive operations overhead

2017

Security constraints all the way

2017

Testing complexity, and debugging nightmares

2017

Effort duplication

2017

Reliability complexity

2017

To embrace microservices, you must be this tall:

2017

Mature organization and team(s)

2017

Good DevOps practices

2017

Observe and adjust, be pragmatic

2017

Write and respect contractsCommunicate

2017

Think about backward compatibility

2017

Monitor, log and trace(in a distributed way)

2017

Design for failure

2017

Optionally (but nice to have) understand DDD and CQRS

2017

Stop building systems and projects, start building products and

cohesive teams

2017

Remember: Microservices have a cost.

Only use it when appropriate

2017

https://inovia.fr - @inoviateamJC Bohin - @bohinjc