The development difficulty of an application with many lines of code is well-known. Whenever several teams need to work on the same source code, there are going to be collisions and a waste of time. To deal with these and other problems, teams employ the microservices architectural approach. In this talk we will discuss microservices, continuous delivery and how teams can work in such setup

1. MICROSERVICES:
A JOURNEY OF AN ETERNAL IMPROVEMENT
Levi9 Meetup 04.2016
Anton Udovychenko

2. ABOUT ME
Software Architect @ Levi9
8+ years of Java experience
Passionate about agile methodology and clean code
http://ua.linkedin.com/in/antonudovychenko
http://www.slideshare.net/antonudovychenko

3. Amsterdam
Levi9 HQ
Amsterdam – 2005
25 people
Novi Sad
Serbia
Novi Sad – 2005
320+ people
Zrenjanin
Serbia
Zrenjanin– 2014
30+ people
Iasi
Romania
Iasi – 2007
80+ people
Kiev
Ukraine
Kiev – 2008
130+ people
http://www.levi9.com/

4. AGENDA
• Monolith development
• Reflections about Scale cube
• Microservices to the rescue
• Spotify Scrum
• Employ Continuous delivery
• Q&A

6. MONOLITH DEVELOPMENT
• Widely known and described
• Simple development
• Straightforward testing
• Easy deployment
Benefits:

7. MONOLITH DEVELOPMENT
• Grows to be tightly coupled
• Difficult to make changes
• Obstacle for scaling
• Complex to analyze
• Frightens developers
• Hard to change technology stack
Disadvantages:

8. MONOLITH DEVELOPMENT
• Grows to be tightly coupled
• Difficult to make changes
• Obstacle for scaling
• Complex to analyze
• Frightens developers
• Hard to change technology stack
Disadvantages:

9. REFLECTIONS ABOUT SCALE CUBE
X axis – horizontal duplication
Scale by cloning

10. REFLECTIONS ABOUT SCALE CUBE
X axis – horizontal duplication
Scale by cloning

11. REFLECTIONS ABOUT SCALE CUBE
Y axis – functional
decomposition
Scale by splitting
different things
X axis – horizontal duplication
Scale by cloning

12. REFLECTIONS ABOUT SCALE CUBE
Y axis – functional
decomposition
Scale by splitting
different things
X axis – horizontal duplication
Scale by cloning
Near infinite scale
Starting point

14. MICROSERVICES TO THE RESCUE

15. MICROSERVICES TO THE RESCUE

16. MICROSERVICES TO THE RESCUE
Small autonomous services
that work together,
modelled around a business domain

17. MICROSERVICES TO THE RESCUE

18. MICROSERVICES TO THE RESCUE
• Scalability
• Independent deployments
• Polyglot services
• Easier to understand a service
• Decoupling
• Fast development
Benefits:

19. MICROSERVICES TO THE RESCUE
• Distribution performance
• Eventual consistency
• Network security
• Orchestration complexity
• Monitoring and testing
• Code duplication
Disadvantages:

21. CONWAY’S LAW
Organizations which design systems ... are constrained
to produce designs which are copies of the
communication structures of these organizations
Melvin Conway

22. SPOTIFY SCRUM
PO
Squad

23. SPOTIFY SCRUM
PO
Squad
PO
Squad
PO
Squad
PO
Squad

24. SPOTIFY SCRUM
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead

25. SPOTIFY SCRUM
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead

26. Chapter
SPOTIFY SCRUM
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead
Chapter

27. Chapter
SPOTIFY SCRUM
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead
Tribe
PO
Squad
PO
Squad
PO
Squad
PO
Squad
Lead
Chapter
Guild

28. CONTINUOUS INTEGRATION
Build
Deploy
Test

29. CONTINUOUS DELIVERY
Build
Deploy
Test
Manual
Acceptance
Release

30. CONTINUOUS DEPLOYMENT
Build
Deploy
Test
Release

31. EMPLOY CONTINUOUS DELIVERY
Version control

32. EMPLOY CONTINUOUS DELIVERY
Version control Continuous delivery
pipeline

33. EMPLOY CONTINUOUS DELIVERY
Version control Continuous delivery
pipeline
Services
v6
v37
v12
v5

34. EMPLOY CONTINUOUS DELIVERY
Version control Continuous delivery
pipeline
Services
v37
v12
v5
Code
changes
v7

35. EMPLOY CONTINUOUS DELIVERY - PIPELINE
BUILD TEST RELEASE
Features:
• Pipeline as code

36. EMPLOY CONTINUOUS DELIVERY - PIPELINE
BUILD TEST RELEASE
Features:
• Pipeline as code
• Auto build versioning
• Manual contracts versioning• Compile
• Version
• Unit test
• Static code
analysis
• Static security
code analysis

37. EMPLOY CONTINUOUS DELIVERY - PIPELINE
BUILD TEST RELEASE
Features:
• Pipeline as code
• Auto build versioning
• Manual contracts versioning• Compile
• Version
• Unit test
• Static code
analysis
• Static security
code analysis
• e2e
• Performance
• Integration
• Penetration
• Contracts

38. EMPLOY CONTINUOUS DELIVERY - PIPELINE
BUILD TEST RELEASE
Features:
• Pipeline as code
• Auto build versioning
• Manual contracts versioning• Compile
• Version
• Unit test
• Static code
analysis
• Static security
code analysis
• e2e
• Performance
• Integration
• Penetration
• Contracts

40. EMPLOY CONTINUOUS DELIVERY - PIPELINE
BUILD TEST RELEASE
Features:
• Pipeline as code
• Auto build versioning
• Manual contracts versioning
• Immutable infrastructure
• Compile
• Version
• Unit test
• Static code
analysis
• Static security
code analysis
• e2e
• Performance
• Integration
• Penetration
• Contracts
Create
env
Run tests
Dispose
env

41. EMPLOY CONTINUOUS DELIVERY - PIPELINE
BUILD TEST RELEASE
Features:
• Pipeline as code
• Auto build versioning
• Manual contracts versioning
• Immutable infrastructure
• Compile
• Version
• Unit test
• Static code
analysis
• Static security
code analysis
• e2e
• Performance
• Integration
• Penetration
• Contracts
• Make available
downstream
• Trigger
integration build
Create
env
Run tests
Dispose
env

42. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53
6
36
11
5
Release
6
36
11
5
53

43. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53
6
36
11
5
Release
6
36
11
5
53
37 37

44. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53
6
36
11
5
Release
6
36
11
5
53
38 38

45. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53
6
36
11
5
Release
6
36
11
5
53
38
12 12

46. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53 54
6 6
36 36
11 12
5 5
Release
6
36
12
5
54
38
12

47. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53 54
6 6
36 36
11 12
5 5
Release
6
36
12
5
54
3939

48. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
53 54 55
6 6 6
36 36 39
11 12 12
5 5 5
Release
6
39
12
5
55
39

49. EMPLOY CONTINUOUS DELIVERY
B T Rgit
B T Rgit
B T Rgit
B T Rgit
B T R+
Release
6
39
12
5
55
39
5555
5656
5757
585858

50. EMPLOY CONTINUOUS DELIVERY
git
git
git
git
+
Future proof:
• Any configuration of squads
• Growing number of components

51. EMPLOY CONTINUOUS DELIVERY
git
git
git
git
+
Future proof:
• Any configuration of squads
• Growing number of components

52. EMPLOY CONTINUOUS DELIVERY
git
git
git
git
+
Future proof:
• Any configuration of squads
• Growing number of components
git

53. TRY MICROSERVICES
http://jhipster.github.io

55. TRY CONTINUOUS DELIVERY
https://www.go.cd/

58. DEMO TIME

59. REFERENCES
http://martinfowler.com/articles/microservices.html
http://microservices.io/articles/scalecube.html
https://ucvox.files.wordpress.com/2012/11/113617905-
scaling-agile-spotify-11.pdf
http://martinfowler.com/articles/microservice-testing
http://blog.arungupta.me/continuous-integration-delivery-
deployment-maturity-model/
http://www.slideshare.net/PavelChunyayev/continuous-
delivery-for-cxp-at-backbase-presented-at-arch9-amsterdam-
30032016-levi9

60. THANK YOU!