When creating application based on architecture of micro services, a team needs to face up many challenges. -building easily extensible architecture of micro services. When we creating new service, we always need data from other service. To be able to receive that data, we only need to import light client, which is the interface of another service. -How to use HTTP protocol properly, to change it to our biggest assets, and do not attempt to hide it unnecessarily. -Which functionalities of monolithic application pull out first. How to use domain driven design, to model the business domain specific for each micro service ? -How to manage configuration and deployment of various services ? -implementing Circuit Breaker patter, using Netfix Hystrix library -real time monitoring of micro services -aggregating logs from many servers in one central point, and analysing them -creating documentation, which could be use as a client of each service

1. Tomasz Lelek
tomekl007
@tomekl007

2. How to rebuild monolithic
application to micro services
architecture?

3. Presentation Plan
1. Business
context
2. Technology
3. Architecture
4. Configura@on
management
5. Monitoring
6. Aggrega@ng
logs
7. Deploying
(
vagrant,
docker
)
8. Modern
documenta@on

4. Monolith

5. Application Domain

6. One entity – multiple identities

7. Same functionality –
new architecture

8. Redirecting request

9. Url Rewriting
#Apache
rewrite
url,
work
for
post
request
RewriteEngine
On
RewriteRule
/generate
hTp://reportservice.no/generate
[P]

10. Needs

11. i

12. Embedded Container

13. Starting Service
./sbt
container:start
[info]
Started
SelectChannelConnector@0.0.0.0:8090
[success]
Total
@me:
2
s

14. How microservice looks like?

15. Using via imported client

16. Many clients

17. Scala java - interoperability

18. Rest, json, http

19. Architecture

20. Architecture Evolve

21. Managing configuration

22. Configuration Service

23. Asking for configuration

24. Switching configuration dynamically

25. Services monitoring - status

26. Monitoring of dependencies

27. Graph visualization

28. Visualization of dependencies

29. Where is service with configuration?

30. etcd

31. Circuit Breaker

32. Hystrix

33. Implementation

34. Many services = many logs

35. One aggregation point

36. + logstash

37. Configuration of Logstash

38. /_search?prettytype=batch-staging

39. Amazon EC2

40. vagrant
plugin
install
vagrant-­‐aws
vagrant
up
-­‐-­‐provider=aws
vagrant
ssh
MACHINE
NAME

42. Technology stack

43. Proper documentation

44. Documentation

45. Generated json

46. Swagger-ui
hTps://github.com/wordnik/swagger-­‐ui

47. Documentation as a client

48. Time for building microservices !

49. Thank You, Questions ?