1. Greg Simons 15/12/2015 Disclaimer: I am not affiliated directly with Cloud Foundry or the Cloud Foundry Foundation Getting started with

2. http://12factor.nethttp://12factor.net (Wiggins) Migrating to Cloud-Native Application ArchitecturesMigrating to Cloud-Native Application Architectures (Stine) MicroservicesMicroservices (Fowler) https://www.cloudfoundry.org/ Stormy Peters @storming Technology Evangelist Cloud Foundry

3.  Elastic infrastructure?  API Provisioning?  Scalable?  Cheaper?  Containers, Virtualisation?

4.  Building an application that is specifically designed to run in a cloud environment.

5. Cloud Native is a way of life!

6.  Speed  Safety  Scale  Client Diversity

7.  Fast Provisioning  Fast delivery  How do I know if we are already fast?  How long would it take for you to get a single line of code in to a production environment?

10.  Building a Production ready application architecture that’s:  Highly available (100%) not the 5 9’s approach  So how do we do this?

12. It’s all about the Open Source

13. Used to be about code. About cost savings Now that’s table stakes.

14. Mobile Clients

15. We see a world of cloud computing that is UBIQUITOUS and FLEXIBLE supporting public, private, and hybrid application environments. PORTABLE and INTEROPERABLE enabling users to move their applications wherever they need to go. VIBRANT and GROWING underlying a massive ecosystem of applications and developers based on an efficient marketplace.

16.  12 factor  Microservices  Anything else?

17.  Single deployable unit not the collective “Application”

18. 1) Codebase 2) Dependencies 3) Config 4) Backing services 5) Build, release, run 6) Processes 7) Port Binding 8) Concurrency 9) Disposability 10) Dev/Prod Parity 11) Logs 12) Admin Processes Traditional App 12 Factor App Time between deploys WeeksHours Code authors v code deployers Different people Same people Dev v Prod DivergentAs similar as possible

19. No, provided your Organization is ready and willing to change!!!

20.  Team structure  Less dependency on tech stack (microservices)  DevOps (IaaS > PaaS)  Application Release Automation  API Provisioning

21.  Without organisational change  We end up missing points of the value behind the Agile Manifesto

22.  Release boards, approval boards, committees  “can” hinder speed, increase cost to delivery!

24. Gold Silver

25. Prescriptive Assembly CHRONOS runC scheduler.next gorouter Cloud Controller Auth Loggregator Staging Buildpacks BOSH Service Broker Diego etcd Core Services container.next

26. Carrier Networking Datacenter Networking Datacenter Operating Systems Hardware Virtual Machines Operating Systems Application Platforms Programming Frameworks Containers

27.  I have Cloud Foundry setup with:  Virtual Box  Vagrant  Bosh-lite http://docs.cloudfoundry.org/deploying/run-local.html

28.  Login  Push  Scale  It’s that easy !

29. DEMO Application

31. Thank you for listening! Greg Simons (Technical Architect) @gregsimons84