Nowdays, every new project that we start is around microservices. You cannot build anymore a simple solution that goes in production in 2 week time. Many times we grow the project complexity because of the current IT trends without thinking about what we need. The focus of the session is around microservices and what is the impact of it during development, automation and operation phase. The purpose is to identify the balance between the size, number and complexity of the services taking into account the delivery time and budget, especially during the first iterations.

1. THE MICROSERVICES
CONFUSION
Radu Vunvulea
Group Head of Cloud Delivery

3. THE MICROSERVICES
CONFUSION
Radu Vunvulea
Group Head of Cloud Delivery

5. 73% OF FIRMS USING OR PLANNING
TO USE MICROSERVICES SEE IT AS
EXTREMELY BENEFICIAL FOR
BUILDING APPLICATIONS
H T T P S : / / D Z O N E . C O M / A R T I C L E S / N E W - R E S E A R C H - S H O W S - 6 3 - P E R C E N T - O F - E N T E R P R I S E S - A R E - A

6. NEARLY TWO-THIRDS OF THE
ORGANIZATIONS SURVEYED (63%)
ARE BUILDING SOME (18%) OR ALL
(46%) OF THEIR APPLICATIONS USING
MICROSERVICES.
H T T P S : / / D Z O N E . C O M / A R T I C L E S / N E W - R E S E A R C H - S H O W S - 6 3 - P E R C E N T - O F - E N T E R P R I S E S - A R E - A

7. HTTPS://TSH.IO/STATE-OF-MICROSERVICES-2020-BY-TSH.PDF

8. MARKET SKILLS

9. HTTPS://TSH.IO/STATE-OF-MICROSERVICES-2020-BY-TSH.PDF

10. STORY TIME
WE ALL LOVE STORIES

12. REST API
TIME UPDATE
TELEMETRY

13. Access Control
Time Update Data Collector
Data Sink
Time Provider
Data
Transformer
Telemetry
Router
…
…

14. Access Control
Time Update Data Collector
Data Sink
Time Provider
Data
Transformer
Telemetry
Router
…
…

15. Access Control
Time Update Data Collector
Data Sink
Time Provider
Data
Transformer
Telemetry
Router
…
…

16. Access Control
Time Update Data Collector
Data Sink
Time Provider
Data
Transformer
Telemetry
Router
…
…
AUTOMATION

17. Size Number Type Complexity Communication Automation

19. WAYS OF WORKING

21. Scalability Performance
BOOST
Teamwork Integration
HINDER

22. COMPUTATION

24. PURE MICROSERVICE APPROACE
BLEND OF DIFFERENT APPROACHES
SERVELESS
MULTI STACK / MULTI CLOUD
PURE MICROSERVICE APPROACH

25. SERVELESS
MICROSERVICE
RESILIENCE
SELECTIVE SCALABILITY
EASIER TO ADD OR UPDATE FEATURES
FLEXIBILITY FOR DEVELOPERS
BETTER SCALABILITY
IMPROVED FLEXIBILITY
MORE EFFICIENT
COST
LARGER AND DO MORE THAN A FUNCTION

26. SERVERLESS MICROSERVICES
SERVELESS
MICROSERVICE FUNCTIONMI CRO SER VICE
MICROSERVICE SERVELESS

27. COMMUNICATION

30. COMMUNICATION
HTTP?S?
EVENTS
gRPC
WEBSOCKETS
MESSAGES
SYNCRONOUS
HTTP?S?
MESSAGES

31. DEBUGGING AND MONITORING

33. (ONLY) LOGS (27%) 85%
DON’T SHOW YOU EVERYTHING
MAINTENANCE AND DEBUGGING

34. SCOPE OF THE
SERVICE
PREDICTING OF
MICROSERVICES
APPROACH
PERMISSIONS
MONITORING
FAULT TOLERANCE
TRACEABILITY
TO SMALL SERVICES
MICRO-TRANSACTIONS
OOP CLASS ORIENTED
***SERVICE APPROACH

35. AUDITING WHAT | WHEN | WHERE | FROM | WHO | ON
WHATFALCO
ABNORMALITY DETECTION

36. MONITORING HEALTH | METRICS | COUNTERS | LOGS
PROMETHEUS | GRAFANA

37. DEBUG STATUS | INIT | LOGS |
CONTAINER | POD
EPHEMERAL CONTAINERS

38. DEBUG
SERVICE EXISTS
SERVICE TEST
SERVICE TO PODS BOUNDING
POD LABEL
SERVICE TO POD PORT MATCHING
1
2
3
4
5

39. DEBUG
(service)
SHELL | IDE
APPLICATION LEVEL

40. MICRO-FRONTENDS

42. MICROSERVICES
PAYMENT
SERVICE
REPORTING
SERVICE
BASCKET
SERVICE
PRODUCT
SERVICE
AGGREGATION LAYER
FRONTEND TEAM
BACKENDDATABASEFRONTEND

43. MICRO-FRONTEND
PAYMENTTEAM
REPORTINGTEAM
BASCKETTEAM
PRODUCTTEAM
BACKENDDATABASEFRONTEND

44. FINAL THOUGHTS

46. MICROSERVICES ARE HERE TO
STAY BUT NOT ALONE
SERVELESS | MICRO-FRONTEND | MONITORING | EVENTS
MASTERS OF IaC, AUTOMATION AND INTEGRATION