This document discusses how to configure infrastructure for a project using various tools like Maven, Gradle, Spring Boot, Docker, and Docker Compose. It notes that while development focuses on business logic and meetings, infrastructure is often neglected due to lack of time and priority. The document then covers build tools like Maven and Gradle, how Spring Boot helps with dependencies and autoconfiguration, how Docker can package applications and ensure consistency across environments, and how Docker Compose can orchestrate multi-container applications and services. It emphasizes taking an infrastructure as code approach and automating processes through continuous integration and delivery.

1. 1

2. 2
How I configure infrastructure of my project
Oleksandr Navka
Lead Software Engineer
23 December 2020

3. 3
Agenda
1. Maven and Gradle
2. Spring Boot
3. Docker
4. Docker compose
5. Continuous integration
6. Test Containers
7. Rest Assured

4. 4

5. 55
Why infrastructure matter?

6. 6
Why infrastructure matter?
Daily activities
1. Meetings
2. Requirements clarification
3. Writing a code that is related to project business logic
But usually, we don't have time for infrastructure

7. 7
Simple tasks
1. Build project
2. Add library
3. Migrate to the new version of the framework
4. Add new type of test
5. Run application on different environments
...or not so simple?

8. 8
How long does it take to introduce a new person to a project?

9. 9

10. 10
Why we don't work on infrastructure
1. Don't have time
2. Other project priorities
3. Don't know how
4. Can't estimate this activity
5. Nobody cares

11. 11

12. 1212
Build tools

13. 13
Build tools
1. Ant
2. Maven
3. Gradle
4. Bazel

14. 14
Build tools
1. Ant
2. Maven
3. Gradle
4. Bazel

15. 15
Build tools
A -> C 2.0
B -> C 2.1
Error
Maven
A -> C 2.0
B -> C 2.1
C 2.1 wins
Gradle

16. 16

17. 17
Infrastructure as a code
For this purpose, we could use mavenw and gradlew

18. 1818
Spring boot

19. 19
Spring boot dependency management
1. Spring boot provides parent pom and bom files to configure libraries
version
2. Spring boot provides starters to add dependencies to your project

20. 20
Spring boot autoconfiguration
Spring Boot autoconfiguration represents a way to automatically configure
a Spring application based on the dependencies that are present on the
classpath.

21. 21

22. 22

23. 2323
Docker

24. 24
Why Docker?
1. Provides the ability to run the application on any system
2. Works on all platforms (Windows also)
3. “Locally works fine” will be not so popular

25. 25
How to add a docker to project
1. Write Dockerfile
2. Build docker image
3. Run docker container

26. 26
Dockerfile
FROM openjdk:15
COPY build/libs/*.jar app.jar
ENTRYPOINT ["java", "-jar","/app.jar"]

27. 27
Build and run
docker build -t my-project-image-name .
docker run -p 8080:8080 my-project-image-name

28. 28
Docker minimal set of commands
• docker build
• docker run (-d, -p, --rm)
• docker start
• docker rm
• docker rmi
• docker container ls
• docker image ls

29. 2929
Databases and other environment

30. 30
What about databases, message brokers etc.?

31. 31

32. 3232
Summary
• Try to use infrastructure as a code approach
• Use docker-compose as much as possible
• Try to automate processes and use CI/CD
• Don't hesitate and use new libraries/frameworks
• Infrastructure should help but not slow down your project

33. 33
Thank you