Slides from my talk about Continuous Delivery / Devops at Kaunas PHP meetup. What it takes to continuously deliver a value? How our team is using extreme programming practices to deliver quality outcome. Task is done only when it's deployed to production!

1. Continuous Delivery
It's done only when it's deployed!
Žilvinas Kuusas KaunasPHP 2017-06-21

2. Twitter: @kuusas
Email: zilvinas@kuusas.lt
Žilvinas Kuusas
lead developer
Estina / ISIGN.io
Me

3. VilniusPHP.lt meetups
NoTrollsAllowed.com
hacker camp
Symfony.lt meetups
CleanPHP.lt trainings & consulting
I make things to happen
CleanPHP.lt

5. I’ll bring some
Extreme
Programming
ideas

6. Continuous Delivery
Edit code > Save & Upload to FTP > Done

7. Where it all began?
ISIGN:
- 3 products
- X shared components
Needs:
- Deploy any time, any version

8. Value oriented
development

9. Quality!

10. How to achieve?

11. It’s all about incremental
development and continuous
improvement

12. Atomic tasks

13. Atomic commits

14. Should be easy to
review

15. Fast to test

16. Deployable to prod

17. Avoid long-living
branches

18. Avoid
versioning
trees

19. Deployed == delivered

20. Developer’s
satisfaction level

21. Business can provide
quick and effective
feedback

22. Wait, but
HOW?

23. Everything begins with a ticket
“We need to have ‘premium users’ and ‘free
users’ which will have portal usage limits.
Premium users also will get premium features*,
for which users are going to pay by credit card**”
...

24. Split tasks into small
chunks

25. Splitting payments
- Credit card processing
- Recurring payments
- Invoices

26. Splitting credit card processing
- Credit card processor integration
- Credit card processing:
- On successful payment
- On 3D-secure request
- On success
- On failure
- On unsuccessful payment
- Not enough funds
- Invalid CC
- UI (credit card form)

27. ● Frontend
○ HTML
○ JS
● Backend
○ Data validation
○ Processing
■ Pre …
■ Post ...
○ Persistence
● 3rd party integration
○ Library
○ Bridge

28. It forces you to think
before writing the code

29. Small tasks -
clear intentions

30. Everybody knows
what they are doing:
- Coding
- Reviewing
- Testing
- Deploying

31. It’s easier to focus
on clear goals

32. Focus == Quality

33. Do only what you
need to do.

34. Do not overthink

35. Do not overengineer

36. How small it should be?
One developer - one deployable feature
per day.

37. Way to write
testable code

38. Quality code reviews

39. Distribute workload

40. Reliable and
predictable
releases

41. Improve often,
Refactor often

42. Code design

43. Code design should
be “evolutionary”...

44. ...but some design
patterns you should
know...

45. #1
Dependency Injection
To manage all the mess

46. #2
Strategy
To have interchangable implementations

47. #3
Decorator
Add behaviour to existing objects without class inheritance

48. Tests!
TDD + Functional tests

49. The Process
Look ma, no hands!

50. Deployment pipeline as code
● Bash
● Jenkinsfile
● Ansible

51. Pull request > Build > Deploy
Monitor && Notify

52. Jenkins build pipeline

53. Deployment pipeline
● Build artifact
● Upload to server
● Extract
● Run DB schema migrations
● Switch symlink
● Reload web server configuration
● Run smoke tests

54. Build better products!

55. Klausimai?