by Filippo Liverani - Grazie al fatto che molti dei valori e dei principi del movimento DevOps sono in comune con quelli di Extreme Programming, negli ultimi siamo riusciti ad applicare anche molte dellle pratiche in un contesto più ampio di quello nel quale erano state concepite. In questa sessione mi piacerebbe condividere il percorso che ho seguito per sviluppare una nuova infrastruttura in TDD e per arrivare ad un processo automatico in grado di deployare in produzione tutti i cambiamenti con un click.

1. Continuous
Delivery
on
PaaS

2. Filippo Liverani
@filippo

3. Continuous Delivery

4. why?

5. build the right thing
photo credit https://www.flickr.com/photos/lifeasart/271751746/

6. photo credit https://www.flickr.com/photos/oskay/253010234/
reduce risk

7. photo credit https://www.flickr.com/photos/8011986@N02/2965137520
measure real progress

8. how?

9. collaboration
photo credit https://www.flickr.com/photos/fncll/145149313/

10. automation
photo credit https://www.flickr.com/photos/sea-turtle/6508782929

11. trunk based development
photo credit https://www.flickr.com/photos/rogerjones/5248044039

12. deployment pipelines

13. Commit
Unit tests
Integration tests
Stress tests
User tests
Acceptance
tests
Production
confidence

14. Platform as a Service

15. service models
software - SaaS
complexity flexibility
platform - PaaS
infrastructure - IaaS
data center

16. private vs public
photo credit https://www.flickr.com/photos/oldpatterns/6100020538/

17. benefits
rapid development
easy to setup
easy to scale
short-term costs
consistency

18. drawbacks
limited flexibility
vendor lock-in
integrations
long term-costs

19. Continuous
Delivery
♥
PaaS

20. accelerators
production-like environments
automated provisioning
automated deployment

21. PaaS in practice!
photo credit href="https://www.flickr.com/photos/quadrapop/32118237/"