Are you in the project which needs ten thousand auto-scaled docker containers on Kubernetes in a multi-regional AWS deployment? Right.. we also have never done that. Nevertheless, you still might need DevOps 'magic' to deliver those boring everyday IT projects on time and budget. I will tell our journey with DevOps at a small IT shop and share tools & practices we have tried and which of them were useful and which were total overkill. Ilgvars is founder & developer at FinoTech. He's been working in IT field for more than 15 years and still kind of enjoys it. Things he likes even more: cooking & eating, few sports activities and finally beer.

1. Practical DevOps

2. About us
FinoTech

3. No IT hipsters
allowed

4. Usual project
Web app
Backoffice
app
Backend
3rd party
integrations
Database
Backend

5. What is
DevOps?
By Wikipedia

6. What is
DevOps?
By Janis Orlovs

7. What our
customers say?
WTF IS THAT?

8. What our
customers care
about?
QUICK
CHEAP
AND IT WORKS

9. It’s all about productivity!

10. How we do it
ARCHITECTURE
TECH STACK
CODING
QA
DEPLOYMENT
SUPPORT

11. Architecture MODULAR
MONOLITH

12. End product
Module A Module B Module C Module D
Single app

13. What about
microservices?
SERIOUSLY?

14. microservices = macro headaches

15. Tech. stack BORING!

16. No IT hipster’s
opinion allowed

17. Tech. stack - database
Can PostgreSQL do it?
YES
Pick PostgreSQL
Read PostgreSQL docs
NO

18. Tech. stack - messaging queue
Can PostgreSQL do it?
YES
Pick PostgreSQL
Read PostgreSQL docs
NO

19. Tech. stack - backend development
Do I know Java?
YES
Use Java
Learn Java
NO

20. Tech. stack - web development
It’s a mess

21. Coding GET THE SHIT DONE!

22. Coding
● Small independent modules
● Clear interfaces
● Minimize inter-dependencies
● Don’t abstract too much
● It’s ok to copy-paste (sometimes)
● Try to avoid data updates and deletes
● Avoid caching
● Resilience

23. QA

24. QA
● Unit tests are mostly useless
● Integration / functional tests rule!
● Support test parallelization
● Test on production-like data
● Manual testing is a must
● Works on my machine --> works on production

25. Deployment STRAIGHTFORWARD

26. Build
● My machine can be a build “server” as well
● Setup CI just before project goes live
● Gradle 4.x is awesome
● Jenkins is ok (with Jenkinsfile)
● Docker sucks

29. Deployment
● It’s ok to deploy from local machine (sometimes)
● Deploy from CI when project is in production
● Use PostgreSQL as-a-service if possible
● Automate DB migration
● Deploy daily

30. ansible-playbook -i my-product deploy.yml

32. Tools we like
● Ansible
● Google Cloud
● Cloudflare

33. Tools we didn’t like or need
● Docker
● Kubernetes
● Terraform
● AWS

34. Support FUN PART

35. Support
● We rarely have tech. related issues
● Easier with simple tech. stack
● Be able to to fix issue & deploy in less than an hour
● Having a team of only full-stack dev(ops) helps a lot
● Extensive logging, data audit logs
● Read logs files during morning coffee

37. Support - hard things
● Writing documentation
● Patience. Explain customer why things work as they do
● 3rd party integrations
● To avoid ‘temporary’ solutions
● Remove unused features

38. Tools we like
● Slack
● UptimeRobot
● Logentries

40. Final words vs

41. Thank you! ilgvars.jecis@fino.tech
(we are not hiring)