Microservices
Beauty and the beast
Lead Engineer @
@francmichal
www.mfranc.com
Michal Franc
TRAINER | ENGINEER | SPEAKER
IT 'Evolution'
http://www.iceland24blog.com/
https://auth0.com/
No Silver Bullet
Why Hype?
Beauty
Beast
Microservices
- Easily replacable
- single deployable
- one business / technical capability
- devops enabled*
- messaging based
*Self Service Agile Infrastracture
Architecture
https://www.nginx.com/blog/
Beauty
Scalability
Independence
Flexibility
Scalable
Works well on small data set, number of requests as working on large ones
can handle increased loads of work
scalable system is system that you can easilly expand so that it can handle more reuquests, work
Scaling Monolith
Vertical
Scaling Monolith
Horizontal
Y axis
functional decomposition
Z axis
data partitioning
Flexible
surgical scalability
Monoliths are scalable but there are limits, Microservices are much more scalable but there are costs
Flexibility
-
Independent Tech
-
Independent development
-
Independent deployments
-
Independent Teams
Freedom
Beast
Cargo Cult
Do you really need micro-services?
https://stackexchange.com/performance
Network Layer
-
latency
-
complexity
-
debbuging
-
security
-
connectivity
Assume that there will be problems
You can't beat the nature of the network
Defensive design and coding
Micro monolithic Architecture
DB as Integration Layer
Code structure follows data model
Distributed data model will encourage distributed code
Microservices =/= technology
Adopting microservices requires changes in the team structure and culture
Distributed system require 'distributed' teams
DevOps?
-
monitoring
-
alerting
-
logging
-
infrastructure as a code
Quick Summary
Microservices
Tool
Monolith
Tool
Microservice
== Costly Tool
To solve problems
And Generate Profits that cover the Costs
The first rule of distributed systems is don’t distribute your system until you have an observable reason to
QA
Thank you
@francmichal
www.mfranc.com
Microservice
By Michal Franc
