PyBay 2018: Production-Ready Python applications

0fe4657094b62f41fb86888015817359?s=47 Michael
August 19, 2018

PyBay 2018: Production-Ready Python 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 for Python applications? This session will explore how to expertly deploy your Python micro-service to production.

0fe4657094b62f41fb86888015817359?s=128

Michael

August 19, 2018
Tweet

Transcript

  1. 2.

    Today’s agenda 1 Introduction 2 Tenets of Readiness 3 Building

    Production-Ready Python Applications 4 Recap
  2. 4.

    Michael Kehoe $ /USR/BIN/WHOAMI • Staff Site Reliability Engineer @

    LinkedIn • Production-SRE Team • Funny accent = Australian + 4 years American • Worked on: • Networks • Micro-services • Traffic Engineering • Databases • Satellites
  3. 5.

    Production-SRE Team @ LinkedIn $ /USR/BIN/WHOAMI • Disaster Recovery -

    Planning & Automation • Incident Response – Process & Automation • Visibility Engineering – Making use of operational data • Reliability Principles – Defining best practice & automating it
  4. 6.

    Production-Ready Python Applications • This talk is a high-level overview

    of what it takes to build a production-ready service • Each of the topics could be its own separate talk • Focus on standard open-source options • Number of options not mentioned
  5. 9.

    “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. 10.

    “… 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. 12.

    Tenets of Readiness 1 Stability 2 Reliability 3 Scalability 4

    Performance 5 Fault Tolerance 6 Disaster Recovery 7 Monitoring 8 Documentation
  8. 14.
  9. 15.

    Tenets of Readiness STABILITY • Stable development cycle • Code

    Linting • Code Review • Central Repository • Build system • See Fabio Fleitas’s talk from Saturday
  10. 16.

    Tenets of Readiness STABILITY • Stable deployment cycle • Canary/

    Staging environment • Reliable Deployment via: • Docker/ Kubernetes • Heroku • CD tools
  11. 18.

    Tenets of Readiness RELIABILITY • Dependency Management • Onboarding +

    Deprecation procedures • See Documentation section • Routing + Discovery • Etcd • PyDiscover • Consul-service-discovery
  12. 20.

    Tenets of Readiness SCALABILITY • Understanding growth-scales • Qualitative vs

    quantitative growth scale • Resource awareness • Dependency scaling • What services/ databases need to scale
  13. 22.

    Tenets of Readiness PERFORMANCE • Constant performance evaluation • Understand

    how to benchmark application • Traffic management • Understand traffic pattern performance • Capacity Planning • Have the right metrics
  14. 24.

    Tenets of Readiness FAULT TOLERANCE • Avoiding Single Points of

    Failure (SPOF) • Use multiple instances behind a load balancer • Catch exceptions (meaningfully)
  15. 25.

    Tenets of Readiness FAULT TOLERANCE • Resiliency Engineering • Add

    testing to verify that non-standard behavior is handled correctly • Run chaos experiments: • DNS/ Network failures • Consume disk space/ IO • Consume CPU
  16. 27.

    Tenets of Readiness DISASTER RECOVERY • Understand common failures •

    Have an application-specific disaster- recovery plan in place • Have a general incident management plan
  17. 33.

    Tenets of Readiness MONITORING: TRACING • Multiple (free/ open-source) Options

    • Opentracing • Jaeger • Zipkin (various community libraries)
  18. 37.

    In-Code Documentation What you should be covering • Function/ API

    & Class docstrings • Code usage documentation • Project documentation • Onboarding • Contribution • Testing
  19. 38.
  20. 44.

    Documentation • Relevant PEP’s: • PEP -257: Docstring Conventions •

    PEP-287: reStructured Docstring Format (Official Python Documentation Standard) • Further info: • https://pythonhosted.org/an_example_p ypi_project/sphinx.html • https://realpython.com/documenting- python-code
  21. 45.
  22. 46.

    Tenets of Readiness 1 Stability 2 Reliability 3 Scalability 4

    Performance 5 Fault Tolerance 6 Disaster Recovery 7 Monitoring 8 Documentation
  23. 47.

    Further Resources • Find me at: • michael-kehoe.io • @matrixtek

    • linkedin.com/in/michaelkkehoe • Slides will be available in multiple locations shortly
  24. 48.