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

Building Production-Ready Applications

November 07, 2018

Building Production-Ready Applications

In 2016, Susan Fowler released the 'Production Ready Microservices' book. This book sets an industry benchmark on explaining how microservices should be conceived, all the way through to documentation. So how does this translate actionable items? This session will explore how to expertly deploy your microservice to production. The audience will learn best practice for designing, deploying, monitoring & documenting application. By the end of the session, attendees should feel confident that they have the knowledge to deploy a service that will be reliable and scalable.


November 07, 2018

More Decks by Michael

Other Decks in Technology


  1. This Is The Only Slide You May Need a Picture

    Of slideshare.net/MichaelKehoe3
  2. Today’s agenda 1 Introductions 2 Tenets of Readiness 3 Creating

    Measurable guidelines 4 Measuring readiness 5 Key Learning’s 6 Q&A
  3. Michael Kehoe $ WHOAMI • Staff Site Reliability Engineer @

    LinkedIn • Production-SRE Team • Find me online at: • @matrixtek • https://michael-kehoe.io • linkedin.com/in/michaelkkehoe
  4. Production-SRE Team @ LinkedIn $ WHOAMI • Disaster Recovery -

    Planning & Automation • Incident Response – Process & Automation • Visibility Engineering – Making use of operational data • Reliability Principles – Defining best practice & automating it
  5. “A production-ready application or service is one that can be

    trusted to serve production traffic…” S U S A N J . F O W L E R
  6. “… We trust it to behave reasonably, we trust it

    to perform reliably, we trust it to get the job done and to do its job well with very little downtime.” S U S A N J . F O W L E R
  7. How did we get here? Monoliths broken down into smaller

    applications Microservice architecture Developers can commit & deploy code faster Continuous Integration Teams supporting a larger number of applications Ops team support
  8. Tenets of Readiness 1 Stability & Reliability 2 Scalability &

    Performance 3 Fault Tolerance & DR 4 Monitoring 5 Documentation
  9. Tenets of Readiness STABILITY • Stable development cycle • Continuous

    Integration • Reproducible builds • Unit/ Integration testing • Stable deployment cycle • Simple repeatable deploys • Canaries/ Dark Canaries/ Staging
  10. Tenets of Readiness FAULT TOLERANCE • Avoiding Single Points of

    Failure (SPOF) • Resiliency Engineering
  11. Tenets of Readiness MONITORING • Dashboards + Alerting for: •

    Service • Resource Allocation • Infrastructure • All alerts are actionable and have pre- documented procedures. • Logging
  12. Tenets of Readiness DOCUMENTATION • Have one central landing-place for

    documentation for the service • Review of documentation from Engineer/ SRE/ Partners • Reviewed Regularly
  13. Tenets of Readiness DOCUMENTATION • What should documentation include: •

    Key information (ports/ hostnames etc) • Description • Architecture Diagram • API description • Oncall information • Onboarding information
  14. Creating Measurable Guidelines • Not all guidelines directly translate into

    something measurable • You may need to look outcomes of specific guidance to create measurable guidelines
  15. Creating Measurable Guidelines EXAMPLE • Stable development cycle à Is

    the unit-test coverage above X %? à Has this code-base been built in the last week? à Are all the library dependencies up-to- date?
  16. Creating Measurable Guidelines EXAMPLE • Stable deployment process à Has

    the application been deployed recently? à What is the successful deployment percentage? à Is there a staging environment for the application?
  17. Measuring Readiness WHY? Ensuring that services are built and operated

    in a standard manner Standardization Ensuring that services are trustworthy Quality Assurance
  18. Measuring Readiness HOW? Create a manual checklist Manual Checklists Automate

    the discovery and measurement of readiness Automated Scorecards
  19. Key Learnings A set of guidelines for what it means

    for your service to be ‘ready’ Create Automate the checking and scoring of these guidelines Automate Set the expectation between Engineering/ Product/ SRE that these guidelines have to be met Evangelize