Talk by Rémi Dewitte, Architect & Consultant at FABERNOVEL TECHNOLOGIES

1. 1//
What is MICRO by
the way?

2. 2//
Rémi Dewitte
Architect & Consultant
@ Fabernovel Technologies
Design Digital Platforms
Move applications to the Cloud
Deploy the bi-modal IT
Design API

3. 3//
Microservices
Netflix

4. 4//
The Monolith

5. 5//
Microservices

6. 6//
Evolvability to change (quickly)

7. 7//
Scalability (selectively)

8. 8//
Resilience

9. 9//
Composability

10. 10//
Monolith / microservices
Cross-cutting concern in all microservices
Many services to operate
Communication through the network
Microservices do not share the CPU&RAM
Coupling is more explicit
Dependencies are harder to introduce “by
mistake”
Cross-cutting concern already in one
place
Only one service to operate
Communication between modules shall
be fast but all modules share the memory
Coupling is easy
Dependencies are easy to introduce

11. 11//
The journey to microservices
Teams productivity
Operability
Architecture
fitnesses

12. 12//
How much micro
from a TEAM point
of vue?

13. 13//
Teams Coordination
Coordination ⇒ Increased cycle lengths

14. 14//
Team Autonomy

15. 15//
Team Autonomy
Reduced cycle lengths (expected)

16. 16//
Team Autonomy & Time to Deliver

17. 17//
Team Autonomy & Time to deliver

18. 18//
How to find the
boundaries?

19. 19//
Domain Driven Design (DDD) Approach
Order Management
Product
Management
Delivery
Management
Client
Knowledge
Marketing
Operations
Management
Warehouse
Management
Supply Chain
Management
Fraud
Detection
Bounded Contexts

20. 20//
Domain Driven Design (DDD) Approach
Domain 1 Data
& Processes
Domain 2 Data
& Processes
Domain 3 Data
& Processes
Domain 4 Data
& Processes
Concept
Digital
Marketing
Packaging
Prices
Stock
Information
Product

21. 21//
Technological Approach

22. 22//
Scalability approach

23. 23//
Build or Use Approach
The functions I need to cover
The APIs and solutions I might use
Online Payment
Event Registration
Emails campaigns
Marketing Automation
360° Customer View
Editorial Content Authoring
Online Payment
The services I need to build
Ad Serving
Ad Serving

24. 24//
How much MICRO
can you manage?

25. 25//
Operate all the services
S
DB
Users
LBLB
Mon
Met
Log Log
Backup
Log
Met Met
Mon
S S S
S S
S
S S S
S S S S S
Backup
DB DB DB
DB DB DB DB
DB
Backup Backup
DB DB DB
DB DB DB DB
S S S S
S S
S
S S S
S S S S S

26. 26//
Automation = *aaS
(!= Use Public Cloud Providers)
SaaS ServicesPaaS “Classic” operations
IaaS
FaaS
“Classic”
Provisionning

27. 27//
All the things to consider...
Discovery
Load Balancing
Communication
● Automatic retries
● Timeout controls
● Back pressure
● Rate limiting
● A/B testing / traffic shaping / request
shadowing
● Service refactoring / request shadowing
Security
● Security between services
● Edge gateway/router
● Forced service isolation (policies)
● Service deadline/timeout enforcement across
service calls
Configuration
Observability
● Log aggregation
● Application metrics
● Audit logging
● Distributed tracing
● Exception tracking
● Health check API
● Log deployments and changes

28. 28//
Operate microservices
Number of units to
operate
Automation
need OK
Risky
Engineering effort

29. 29//
The journey to microservices
Teams productivity
Operability
Architecture
fitnesses
Keep the balance

30. 30//
Any questions?