Java Day Minsk 2016 Keynote about Microservices in real world
3 likes956 views
Slides from #javaday #keynote about microservices. Everyone has heard about microservices. Someone tries to implement them in practice. And only the bravests of us have already used them in production environment.But then why so many people hype around microservices, if the idea is not quite new? What are microservices? What is the difference between it and good old SOA approach? How can developers create modern enterprise applications in Java easily with the help of this approach? We discuss about history of microservices, share our practical experience, and try to find answer for question "How to use microservices approach in production"
![~home > lazybones create api 0.0.1 rent-service
Creating project from template api 0.0.1 in 'rent-service'
Define value for 'group' [by.javaday]:
Define value for 'version' [0.0.1]:
srv1
├──srv2
└──srv3
logging
sleuth
Define value for 'dependencies' [logging,sleuth]:
Project created for rent-service!
68](https://image.slidesharecdn.com/javaday-160611080239/85/Java-Day-Minsk-2016-Keynote-about-Microservices-in-real-world-68-320.jpg)
![Not so smart
= This is main documentation
This document describes how to be the most fundamental and important document
in the world of documents
include::https://raw.github.com/asciidoctor/asciidoctor/master/Gemfile[]
include::../other.adoc[]
include::/home/tolkv/git/docs-0/superdoc.adoc[]
79](https://image.slidesharecdn.com/javaday-160611080239/85/Java-Day-Minsk-2016-Keynote-about-Microservices-in-real-world-79-320.jpg)
![Really smart
= This is main documentation
This document describes how to be the most fundamental and important document
in the world of documents
include::https://raw.github.com/asciidoctor/asciidoctor/master/Gemfile[]
include::gradle://gradle-advanced:service-with-deps:1.0/deps.adoc[]
include::gradle://:service/doc.adoc[]
80](https://image.slidesharecdn.com/javaday-160611080239/85/Java-Day-Minsk-2016-Keynote-about-Microservices-in-real-world-80-320.jpg)
![Payment Service[jar,doc] Insurance Service [jar,doc]
One Point of View
[UberDoc.zip]
Rent Service[jar,doc] Other Service [jar,doc]
Information Aggregation
81](https://image.slidesharecdn.com/javaday-160611080239/85/Java-Day-Minsk-2016-Keynote-about-Microservices-in-real-world-81-320.jpg)
![./gradlew deployToArtifactory
ansible -i [stage,dev,test] -t deploy
Predefined Configuration
92](https://image.slidesharecdn.com/javaday-160611080239/85/Java-Day-Minsk-2016-Keynote-about-Microservices-in-real-world-92-320.jpg)
![Curse of spring boot test [VRN]](https://cdn.slidesharecdn.com/ss_thumbnails/curseofspringboottest-171009150100-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
Similar to Java Day Minsk 2016 Keynote about Microservices in real world (20)
More from Кирилл Толкачёв (12)
Ad
Recently uploaded (20)
Ad
Java Day Minsk 2016 Keynote about Microservices in real world
- 1. Микросервисы огонь, вода, медные трубы 1
- 5. 5
- 6. 6
- 7. “Microservices” - just a buzzword 7
- 8. “Microservices” - just a buzzword 8
- 9. Why? ● High abstraction level 9
- 10. Why? ● High abstraction level ● Popular word 10
- 11. Why? ● High abstraction level ● Popular word ● Sell itself 11
- 12. Why? ● High abstraction level ● Popular word ● Sell itself ● More talks 12
- 14. 14
- 17. 17
- 18. 18
- 19. What is the architecture? 19
- 20. What is the architecture? 20
- 21. What is the architecture? 21 https://www.youtube.com/watch?v=_Kex5hwGE-w
- 23. 23
- 24. Big Ball of Mud 24
- 27. 12 April 1996 SOA is Born https://www.gartner.com/doc/302868/service-oriented-architectures- 27
- 28. 12 April 1996 SOA is Born https://www.gartner.com/doc/302868/service-oriented-architectures- 28
- 29. SOA Principles 1. Standardized service contract 2. Loose coupling 3. Encapsulation 4. Reusability 5. Autonomy 6. Statelessness 7. Discoverability 29
- 30. Classic SOA ● centralized orchestration ● complicated (hi, SOAP) ● smart pipes (hi, ESB) 30
- 31. 5 January 2009 SOA is Dead http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html 31
- 32. What did you say? 32
- 33. SOA != SOAP (WS-*) 33
- 34. 34
- 35. 35
- 36. ...and what about people? 2004 year 36
- 37. SOA was ahead of its time 37
- 38. 38 SOA So
- 40. Microservices 40
- 41. A=F(Rq, FRq, NFRq,..........???............) DevOps OSS Domination 41
- 43. 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 43
- 44. Does size matter? ● Method/Function = Microservice? ● 10-300 LOC = Microservice? ● 1 week = Microservice? ● 1 developer = Microservice? 44
- 45. Size doesn’t matter* ● 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 *within reason 45
- 47. 47 DDD Dd SOA So
- 48. Microservices are new classes 48
- 49. 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 49
- 50. Problem → So Many Teams 50
- 51. LSD Principle - L programming languages - S average framework count by language - D data source types complexity = L * S * D 51
- 52. Some LSD for you - three programming languages - two average framework count by language - seven data source types - legacy WS, mongo db - OLTP, OLAP - elasticsearch, neo4j - Mishka’s database %) complexity = 3 * 2 * 7 = 42 (!) 52
- 53. What can’t be sacrificed? min (L * S * D) → ? 53
- 54. min (L * S * D) → max (D) 54
- 55. L = Java 18+ S = Spring Boot D = ∞ 55
- 58. N services → 1 DB Isolated by Schema/Tables 58
- 59. N services → N DB Distributed Transactions are Painfull 59
- 60. M services → 1 DB L services → L DB M + L = N, M << L 60
- 61. Event Sourcing / CQRS / SAGAS http://gotocon.com/dl/goto-chicago-2015/slides/CaitieMcCaffrey_ApplyingTheSagaPattern.pdf 61
- 62. java Ja spring boot Sb 62 Data Isolation Di LSD principle Ls DDD Dd SAGAS Sa SOA So
- 63. Problem -> Many Services 63
- 67. lazybones create api 1.0.1 service_name 67
- 68. ~home > lazybones create api 0.0.1 rent-service Creating project from template api 0.0.1 in 'rent-service' Define value for 'group' [by.javaday]: Define value for 'version' [0.0.1]: srv1 ├──srv2 └──srv3 logging sleuth Define value for 'dependencies' [logging,sleuth]: Project created for rent-service! 68
- 69. lazybones Lz yoman Yo start.spring.io Ss java Ja spring boot Sb groovy Gy 69 Data Isolation Di LSD principle Ls DDD Dd SAGAS Sa SOA So
- 70. Problem → DRY off 70
- 71. TServerTransport serverTransport = new TServerSocket( new InetSocketAddress(InetAddress. getLocalHost(), port)); TProcessor processor = new TInsuranceService. Processor<>( //business value here ); server = new TSimpleServer( new TServer.Args(serverTransport).processor (processor)); server.serve(); 71
- 72. TSocket transport = new TSocket(host, port); transport.open(); TBinaryProtocol tBinaryProtocol = new TBinaryProtocol (transport); TInsuranceService.Client client = new TInsuranceService.Client(tBinaryProtocol); perform(client); //business value here transport.close(); 72
- 73. @ThriftController public class InsuranceController implements TInsuranceService.Iface { @Override public void someMethod(TInsurance insurance){ //business value here } } 73
- 74. @ThriftClient(serviceId = "insurance-service") TInsuranceService.Client client; ... perform(client); //business value here ... 74
- 77. documentation → smart documentation 77
- 78. Not smart = This is main documentation This document describes how to be the most fundamental and important document in the world of documents ... COPY-PASTE documentation from another document ... 78
- 79. Not so smart = This is main documentation This document describes how to be the most fundamental and important document in the world of documents include::https://raw.github.com/asciidoctor/asciidoctor/master/Gemfile[] include::../other.adoc[] include::/home/tolkv/git/docs-0/superdoc.adoc[] 79
- 80. Really smart = This is main documentation This document describes how to be the most fundamental and important document in the world of documents include::https://raw.github.com/asciidoctor/asciidoctor/master/Gemfile[] include::gradle://gradle-advanced:service-with-deps:1.0/deps.adoc[] include::gradle://:service/doc.adoc[] 80
- 81. Payment Service[jar,doc] Insurance Service [jar,doc] One Point of View [UberDoc.zip] Rent Service[jar,doc] Other Service [jar,doc] Information Aggregation 81
- 82. Centralization Paradox To work effectively with distributed applications, you need to have a very good centralized libraries and tools. For example: logging, health-checking, metrics, exception handling, documentation autogeneration 82
- 83. Centralization Paradox To work effectively with distributed applications, you need to have a very good centralized libraries and tools. But: don’t do this with you business logic or domain model 83
- 84. lazybones Lz yoman Yo start.spring.io Ss java Ja thrift Th spring boot Sb gradle Gr asciidoctor Ad groovy Gy 84 Data Isolation Di Centralization paradox Cp LSD principle Ls DDD Dd SAGAS Sa Smart Docs Sd Smart Libs Sl SOA So
- 86. war/ear 86
- 92. ./gradlew deployToArtifactory ansible -i [stage,dev,test] -t deploy Predefined Configuration 92
- 95. How we run cluster 95
- 96. More spice! 96
- 97. More spice! 97
- 98. More spice! 98
- 99. Mesos lets us treat a cluster as one big computer WEB WASTED CACHE WASTED WASTED HADOOP 99
- 100. Mesos lets us treat a cluster as one big computer WEB WASTED CACHE WASTED WASTED HADOOP WASTED WEB CACHE HADOOP FREE FREE 100
- 101. lazybones Lz yoman Yo start.spring.io Ss python Py java Ja spring boot Sb gradle Gr asciidoctor Ad docker Dr mesos Ms marathon Ma chronos Ch aurora Au Kubernetes Kb groovy Gy 101 Data Isolation Di Centralization paradox Cp LSD principle Ls DDD Dd SAGAS Sa Smart Docs Sd Dynamic Sharing Ds Smart Libs Sl SOA So ansible An thrift Th Artifactory Ar
- 102. Problem → Find them All 102
- 103. insert into settings_table values (key, endpoint) 103
- 104. update template → services.location kill -s HUP nginx 104
- 106. 106 Service Client Registry-aware HTTP Client Service Registry Service Instance 1 Service Instance N Service Instance ... Load balance request Client side discovery
- 107. 107 Service Client Service Registry Service Instance 1 Service Instance N Service Instance ... Load balance request Router/Proxy Server side discovery
- 108. Problem → Defend yourself 108
- 109. 109
- 110. 110 Circuit Breaker
- 112. 112 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 5мс
- 113. 113 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 300мс
- 114. 114 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 300мс
- 115. 115 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 300мс
- 116. 116 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 300мс
- 117. 117 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 300мс Open
- 118. 118 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 300мс Half-Open
- 119. 119 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 5мс Half-Open
- 120. 120 Хочу бегемота! Rent Service Payment Service Security Service Blockchain Service Insurance Service 5мс
- 121. 121
- 122. Problem → Follow the Trace 122
- 123. No Trace 123
- 124. X-Request-Id = X-Request-Id ?: new ID Good Old ServletFilter 124
- 126. 126 RentService PaymentService SecurityServiceBlockchainService TraceId = X SpanId = A No TraceId No SpanId TraceId = X SpanId = A TraceId = X SpanId = A TraceId = X SpanId = B TraceId = X SpanId = B TraceId = X SpanId = C TraceId = X SpanId = C TraceId = X SpanId = D TraceId = X SpanId = D TraceId = X SpanId = E TraceId = X SpanId = E TraceId = X SpanId = F TraceId = X SpanId = G
- 127. 127
- 128. 128
- 129. 129 RentService PaymentService SpanId = B Client Send SpanId = B Server Received SpanId = B Client Received SpanId = B Server Send TraceId = X SpanId = A TraceId = X SpanId = C
- 130. yoman Yo start.spring.io Ss python Py lazybones Lz java Ja spring boot Sb gradle Gr asciidoctor Ad thrift Th docker Dr mesos Ms marathon Ma chronos Ch aurora Au Artifactory Ar Kubernetes Kb eureka Eu consul Cl etcd Ed zookeeper Zk hystrix Hx sleuth Sl zipkin Zn groovy Gy 130 Data Isolation Di Centralization paradox Cp LSD principle Ls DDD Dd SAGAS Sa Smart Docs Sd Dynamic Sharing Ds Smart Libs Sl SOA So ansible An
- 131. 1. Архитектура функция от множества переменных 2. Всё новое - хорошо забытое старое 3. Микросервисы как iPhone 4. Микросервисы - новые классы 5. Каждой задаче - свой инструмент Запомните это 131
- 132. 1. SOA принципы живы 2. Принцип LSD 3. Изоляция данных делает жизнь приятнее 4. В сложных ситуациях Event Sourcing/CQRS/SAGAS 5. Парадокс централизации 6. Планируй ресурсы динамически Придерживайтесь принципов 132
- 133. Links Spring Thrift Starter: https://github.com/aatarasoff/spring-thrift-starter Тоже, но для grpc: https://github.com/lavcraft/grpc-spring-boot-starter Какие-то примеры: https://github.com/lavcraft/wild-microservices-in-kiev Gradle doc plugin blueprint: https://github.com/aatarasoff/documentation-plugin- demo 133
- 134. Спасибо! Готовы ответить на ваши вопросы @tolkv @aatarasoff 134 @lavcraft @aatarasoff
- 135. Post Scriptum 135
- 136. Event Sourcing / CQRS / SAGA http://gotocon.com/dl/goto-chicago-2015/slides/CaitieMcCaffrey_ApplyingTheSagaPattern.pdf 136
- 137. 137
- 138. 138
- 139. Saga guarantee ● T1 -> T2 -> T3 -> … -> Tn ● T1 -> T2 -> … Tn -> Cn … -> C2 -> C1 139
- 140. 140
- 141. 141
- 142. 142