Two great talks on microservices delivery & management!
6:30 - 7:00: Networking and refreshments
7:00 - 7:45: In-cluster testing for Microservices in Docker containers; Neil Gehani
7:45 - 8:30: Stranger Things: The Forces that Disrupt Netflix; Haley Tucker
In-cluster continuous testing framework for Microservices in Docker containers
Senior Product Manager @ HPE
Just like a tugboat brings containers safely to port, “Tugbot” (open source framework) will do the same for running quality Docker containers in production .
Tugbot makes Continuous Testing REAL. Any kind of test (including performance, chaos, and security) can be run with 5-6 lines in a “Test Container” Dockerfile. Leveraging the Docker LABEL and Docker unified API, we will show how this simplifies testing for services running in docker containers while standardizing results collected for analytics to continuously improve the quality of software. Creating these “test container” Dockerfiles, enables “social testing” for containers like github has done for social coding. As microservices proliferate, the complexities of testing in a real environment with real data will become important than CI, as part of the CD (Continuous Delivery) phase of the lifecycle.
We will demo using the DockerCon16 voting app. We will also demonstrate how to inject chaos into the app to test for resiliency using “pumba” - an open source chaos injection tool.
Stranger Things: The Forces that Disrupt Netflix
Haley Tucker, Senior Software Engineer, Playback Features @Netflix
Imagine a world where you do everything within your power to ensure the code you are pushing into production is as ready as possible to take traffic. You have thorough test coverage, you push out canaries, and you use push windows. You have truly operated your microservice in a top-notch way. And then all of a sudden...CPU spikes, GC churns, latency increases, you start spewing errors...enter sad Netflix customers.
This talk will explore ways in which behaviors of other systems result in surprise issues with your service. It will lay out strategies that you can employ to protect your systems and enable your on call staff to sleep better knowing that things will go wrong, but your system won’t fall over.
In this session:
- Learn how microservice sharding can isolate the impact of outages and enable proper tuning for different use cases.
- Understand the impact of fallbacks on your service and what makes a good fallback.
- Why auto-loading/initializing/binding and package scanning is bad for operations.
- Strategies for “canarying” data changes.While triaging problems, trust nothing!