Upgrade to Pro — share decks privately, control downloads, hide ads and more …

DODDFW2017 - Why You Need to Stop Using THE Staging Server

DODDFW2017 - Why You Need to Stop Using THE Staging Server

Old staging methodology is broken for modern development. In fact, the staging server is left over from when we built monolithic applications. Find out why microservice architectures are driving ephemeral testing environments & why every sized dev shop should deliver true continuous deployment.

Staging servers slow down development with merge conflicts, slow iteration loops, and manhour intensive processes. To build better software faster containers and infrastructure as code are key in 2017. Dev Ops professionals miss this talk at their own peril.

DevOpsDays DFW

August 30, 2017
Tweet

More Decks by DevOpsDays DFW

Other Decks in Business

Transcript

  1. www.codefresh.io Copyright © 2017 All Rights Reserved Why you need

    to stop using THE staging env Chloe Condon- Developer Evangelist at Codefresh
  2. About Chloe ‣ Developer, Mentor/Advocate ‣ Developer Evangelist at Codefresh

    ‣ Blogger of all things container, Docker, and diversity related @ChloeCondon @ChloeCondon
  3. Codefresh is a Docker-Native CI/CD platform for Dev teams. It

    allows teams to automate the process of building, testing, and deploying containerized applications. ABOUT CODEFRESH
  4. develop/staging ✓unit tests ✓unit tests ✓code review pull-request ✓unit tests

    ✓integration test ✓performance test ✓manual testing ✓security testing ✓build & push to registry ✓push to registry ✓deploy to production master COMMON CI/CD PROCESS IMPLEMENTATION
  5. ✓ Code Base ✓ Test Results ✓ Proposed Changes in

    DB ✓ Known Issues WHAT ARE THE DELIVERABLES?
  6. STAGING * STAGING * STAGING * * Staging like environment

    STAGING * STAGING * STAGING * STAGING * DESIGNED FOR MICROSERVICE ARCHITECTURES
  7. DESIGNED FOR MICROSERVICE ARCHITECTURES STAGING * STAGING * STAGING *

    STAGING * STAGING * STAGING * STAGING * * Staging like environment
  8. DESIGNED FOR MICROSERVICE ARCHITECTURES STAGING * STAGING * STAGING *

    STAGING * STAGING * STAGING * STAGING * * Staging like environment
  9. c can be tested earlier c can be tested earlier

    c can be tested earlier c can be tested earlier* DOCKER NATIVE PIPELINE
  10. develop feature-branch ✓unit tests ✓integration test ✓performance test ✓UX ✓unit

    tests ✓integration test ✓performance test ✓ui & manual test ✓UX pull-request ✓unit tests ✓integration test ✓SLA based performance test ✓ui & manual test master DOCKER NATIVE PIPELINE
  11. DOCKER NATIVE ✓ Test every build ✓ Unit, Integration, Security,

    etc ✓ Staging before pull request 24 x FASTER SOFTWARE DEVELOPMENT