My view of the production ready microservices. By the way I prefer nanoservices. microservice-per-host model load balancing worker-based system one microservice per one feature (function) each microservice contains API endpoints, backend and storage (DB) no API versions just Consumer-Driven Contracts behaviors no tight coupling between microservices secured connections between microservices global session UUID for all microservices scalable, reliable, fault-tolerant, performant, monitored, documented, and catastrophe-prepared microservices

1. N D L
Good
microservices
B y B u s h m i n V i k t o r

2. MICROSERVICES
microservice-per-host model
load balancing
worker-based system
one microservice per one feature (function)
each microservice contains API endpoints, backend
and storage (DB)
no API versions just Consumer-Driven Contracts
behaviors
no tight coupling between microservices
secured connections between microservices
global session UUID for all microservices
scalable, reliable, fault-tolerant, performant,
monitored, documented, and catastrophe-prepared
microservices

3. Architecture

4. HOW THEY SHOULD WORK?
MICROSERVICE-PER-HOST MODEL
Easily scale one service
independent from others, and
deal with security concerns
more easily by focusing our
attention only on the service
and host that requires it.
GLOBAL SESSION UUID FOR ALL MICROSERVICES
Tells us who initiated current session
LOAD BALANCING
Allow us to add more instances of our
microservice in a way that is
transparent to any service consumers.
WORKER-BASED SYSTEM
You can spin up additional
instances on demand to
match the load coming in
LOOSE COUPLING
When services are loosely coupled, a change to one
service should not require a change to another.
SECURED CONNECTIONS BETWEEN
MICROSERVICES
Protection against people eavesdropping on the
traffic between the client and server or messing
with the payload

5. monolithic
host
host
host host
host host
MICROSERVICE-PER-HOST MODEL

6. Load Balancer
pool
pool
pool
LOAD BALANCING WORKER-BASED SYSTEM

7. Production
Ready

8. UBER PRODUCTION READINESS
3
2
1
6
7
4
5FAULT-TOLERANT
PERFORMANT
MONITORED
DOCUMENTED
SCALABLE
CATASTROPHE-
PREPARED
microservice
RELIABLE

19. small enough
and no smaller

20. storeprocEP
API endpoint Back DB
Small
One feature per microservice
call
callback
fallback
Stateless
Pure

21. N D L
THANK YOU