Europython 2017: Pythonist View on Microservices and Containerization

This deck is all about what Microservices architecture is and how crucial it is to understand the characteristics of it before putting it as a part of system design. This also covers how microservices can be implemented in Python and the ways it can be deployed.

Transcript

1. MICROSERVICES & CONTAINERIZATION PYTHONIST VIEW ON ABHISHEK SHARMA
2. FULL STACK SOFTWARE ENGINEER @eInfochips About Me abyshek_sharma sharma-abhishek
4. ISN’T IT SAME AS SERVICE ORIENTED ARCHITECTURE (SOA)?
5. MICROSERVICES ARCHITECTURAL STYLE IS A SPECIALISATION OF SERVICE-ORIENTED ARCHITECTURE
6. Minimal Independently deployable Configurable Replaceable Organized around business capabilities Smart Endpoints Elasticity Resilience Versioning Infrastructure Automation Centralized Logging and Monitoring Encapsulation Stateless
7. • Microservice relies on each other public APIs • Decentralised and no single point of failure • Right tool for the right job • Polyglot Persistence • Single Responsibility • Scalability • Decoupled • Bounded Context • End-to-End Ownership and Independent Governance ADVANTAGES OF MICROSERVICES OVER MONOLITHIC/SOA
8. HOW DO YOU WRITE MICROSERVICES IN PYTHON?
10. Supported Protocols: • Simple HTTP GET and POST. • RPC over AMQP • PUB-SUB • WEB SOCKET support Other features: • Support for unit testing service pip install nameko
11. How are services packaged and deployed?
12. • TRADITIONAL (AS IN MONOLITHIC) • VIRTUALIZATION (VIRTUAL MACHINES) • CONTAINERIZATION (DOCKER) DEPLOYMENT OPTIONS
13. DOCKER ARCHITECTURE • Uses Linux Kernel Capabilities ( lxc, libvirt ) To Provide Isolation • Much Lightweight Than Hypervisor (Source: http://itgix.com/blog/post/containerization-with-docker/)
14. IF YOU HAVE DOCKER, DO YOU NEED VIRTUALENV?
15. • Build your Python app • Create a Dockerfile • Build Image • Run Container CONTAINERIZING PYTHON BASED SERVICES WITH DOCKER
16. A SIMPLE FLASK APP
17. CREATE YOUR DOCKERFILE BUILD YOUR DOCKER IMAGE RUN THE DOCKER CONTAINER CONTAINER RUNTIME STATUS
18. CI/CD APPROACH IN MICROSERVICES AND CONTAINERIZATION
19. WHEN TO USE MICROSERVICES?
20. • Shared Database • HTTP is the only protocol • Writing your own service discovery service • Forcing Microservices where it is not required • Logging and Monitoring as an after-thought • One technology and framework everywhere COMMON MISTAKES PEOPLE DO WHEN USING MICROSERVICES
21. • Operational and Tools Cost • Cultural Cost • Distributed System Complexity • Interfaces should be well defined (Documentation is must) • Microservices is devops first architectural style • Team communication overhead TRADE-OFF OF USING MICROSERVICES
22. THANK YOU