The document discusses microservices architecture, emphasizing the development of applications as a suite of small, independently deployable services that communicate through lightweight mechanisms. These services focus on business capabilities and minimize centralized management, adopting various programming languages and storage technologies. It also addresses challenges such as complexity, deployment, service discovery, and the importance of centralized tools for effective operation in distributed systems.

1. WILD microSERVICES
18+

2. @tolkv
2

3. @aatarasoff
3

4. WILD microSERVICES
18+

5. DISCLAIMER
No warranty guarantee
5

6. Agenda
1. Theory
2. Practice
3. Q&A
6

7. 7

8. 8

9. 9

10. Ball of Mud
10

11. SOA Principles
1. standardized service contract
2. loose coupling
3. encapsulation
4. reusability
5. autonomy
6. statelessness
7. discoverability
11

12. 12

13. 13

14. Никто не любит “некрасивые” технологии
поэтому они умирают

15. 15
Про тренды

16. In short, the microservice architectural style is an approach to developing
a single application as a suite of small services, each running in its own
process and communicating with lightweight mechanisms, often an HTTP
resource API. These services are built around business capabilities and
independently deployable by fully automated deployment machinery.
There is a bare minimum of centralized management of these services,
which may be written in different programming languages and use
different data storage technologies.
-- James Lewis and Martin Fowler
Что такое микросервисы?
16

17. In short, the microservice architectural style is an approach to developing
a single application as a suite of small services, each running in its own
process and communicating with lightweight mechanisms, often an HTTP
resource API. These services are built around business capabilities and
independently deployable by fully automated deployment machinery.
There is a bare minimum of centralized management of these services,
which may be written in different programming languages and use
different data storage technologies.
-- James Lewis and Martin Fowler
Что такое микросервисы?
17

18. Размер имеет значение?
● Method/Function = Microservice?
● 10-300 LOC = Microservice?
● 1 week = Microservice?
● 1 developer = Microservice?
18

19. Размер не имеет значения*
● Single Responsibility
● One capability
● Bounded context
“In your organization, you should be thinking not in terms
of data that is shared, but about the capabilities those
contexts provide the rest of the domain.”
– Sam Newman, Building Microservices
*до разумных пределов конечно
19

20. Domain-Driven Design
20

21. In short, the microservice architectural style is an approach to developing
a single application as a suite of small services, each running in its own
process and communicating with lightweight mechanisms, often an HTTP
resource API. These services are built around business capabilities and
independently deployable by fully automated deployment machinery.
There is a bare minimum of centralized management of these services,
which may be written in different programming languages and use
different data storage technologies.
-- James Lewis and Martin Fowler
Что такое микросервисы?
21

22. Process segregation
22

23. In short, the microservice architectural style is an approach to developing
a single application as a suite of small services, each running in its own
process and communicating with lightweight mechanisms, often an HTTP
resource API. These services are built around business capabilities and
independently deployable by fully automated deployment machinery.
There is a bare minimum of centralized management of these services,
which may be written in different programming languages and use
different data storage technologies.
-- James Lewis and Martin Fowler
Что такое микросервисы?
23

24. Независимый деплой
build test
24

25. In short, the microservice architectural style is an approach to developing
a single application as a suite of small services, each running in its own
process and communicating with lightweight mechanisms, often an HTTP
resource API. These services are built around business capabilities and
independently deployable by fully automated deployment machinery.
There is a bare minimum of centralized management of these services,
which may be written in different programming languages and use
different data storage technologies.
-- James Lewis and Martin Fowler
Что такое микросервисы?
25

26. Language/technology segregation
26

27. Data segregation
27

28. Team segregation
28

29. Принцип LSD
- L языков программирования
- S в среднем фреймворков на язык
- D типов источников данных
complexity = L * S * D
29

30. Пример
- три языка программирования
- два в среднем фреймворка на язык
- семь типов источников данных
- legacy WS, mongo db
- хранимые процедуры, JDBC-templates
- elasticsearch, neo4j
- мишкина база
complexity = 3 * 2 * 7 = 42 (!)
30

31. Чем нельзя жертвовать?
min (L * S * D) -> ?
31

32. Закон трёх букв
min (L * S * D) -> max (D)
32

33. Почему Spring Boot/Spring Cloud?
33

34. А теперь попробуем
34

35. 35
Хочу бегемота!

36. Хочу бегемота!
Rent Service
36

37. 37
Хочу бегемота!
Rent Service
Payment Service

38. 38
Хочу бегемота!
Rent Service
Payment Service
Security Service Blockchain Service

39. 39
Хочу бегемота!
Rent Service
Payment Service
Security Service Blockchain Service
Insurance Service

40. Problem -> Many Services

41. Demo -> Bootstrapping

42. Problem -> Delivery value

43. Demo -> Build, Distr, Deploy

44. Problem -> Find them all

45. Service Discovery
45

46. Demo -> Time to Discover

47. Problem -> goto Production

48. Где мой порт?
48

49. 49

50. Какие есть варианты?
● Nginx/Haproxy + consul template
● Haproxy + bamboo (need marathon)
● Netflix Zuul (Java way!!!)
● Custom Servlet <- все с этого начинают!
50

51. Netflix Zuul
51

52. Demo -> Gateway Time

53. Problem -> Defend yourself

54. 54

57. Demo -> Hystrix the Saviour

58. Problem -> Find the Trace

59. 59

60. 60

61. Demo -> Sleuthing

62. Типичная микросервисная архитектура
62

63. 63

64. А что в этих ваших интернетах?
64

65. 65
DDDD (4D)

66. Выводы
66
● Микросервисы - это просто

67. Выводы
67
● Микросервисы - это просто
● Микросервисы - это сложно

68. Парадокс (де)централизации микросервисов
Чтобы эффективно работать с распределенными
приложениями, нужно иметь очень хорошие
централизованные библиотеки/инструменты
Например: логирование, health-чеки, метрики,
обработку программных ошибок
68

69. Парадокс (де)централизации микросервисов
Чтобы эффективно работать с распределенными
приложениями, нужно иметь очень хорошие
централизованные библиотеки/инструменты
Но: не выносите бизнес-логику или доменные объекты
69

70. LSD вам в помощь
min (L * S * D) -> max (D)
70

71. Code. Better. Together.
Примеры сегодняшнего дня
https://github.com/lavcraft/wild-microservices-in-kiev
71

72. Высокие теории
Sam Newman “Building Microservices”
Martin Fowler “Microservice TradeOff” “Microservices”
“The Twelwe-Factor App” http://12factor.net
Hystrix: managing failures in distributed systems - Tomasz Nurkiewicz https:
//www.youtube.com/watch?v=JadVts_prtA
72

73. Спасибо! Готовы ответить на ваши вопросы
@tolkv
@aatarasoff
73