- Go 83.7%
- Dockerfile 7.3%
- HCL 6.4%
- Makefile 2.6%
|
|
||
|---|---|---|
| .vscode | ||
| 1_getting_started | ||
| 2_tracing | ||
| 3_canary | ||
| docs | ||
| gloo-loop | ||
| payment-service | ||
| .gitignore | ||
| consul-values.yml | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| README.md | ||
Service Mesh for the Developer Workflow
Abstract
Service mesh is often presented as a solution for network engineering and system operability, increasing security, reliability, and observability. However, service mesh is also an incredibly useful tool for developers, and understanding how to leverage this technology can dramatically simplify your day to day workflow.
By leveraging free and open-source tools and a scenario-based approach, we will illustrate how a service mesh can help with application resilience, observability, and debugging.
By the end of this workshop you will understand: How to use metrics and distributed tracing effectively Reliability patterns like retries, timeouts, and circuit breaking How to leverage Canary deployments How you can effectively debug distributed systems
The cloud-native, open-source technology used in this tutorial include: Envoy Prometheus Gloo shot Consul Service Mesh Loop Squash Open Census
Requirements
Ideally it will be possible to bundle these tools into a Docker Container to account for for different environments and minimum setup for the user.
- Docker
- Kubectl
- VSCode / Vim
- Squash
- Gloo Shot
- Loop
- Consul (CLI)
Lesson Plan (total 1hr30 mins)
- What is a Service Mesh (10 mins)
- Setting up the environment (10 mins)
- yard up
- install gloo api gateway
- expose service through gateway
- Deploy your first application (10 mins)
- Tracing
- using tracing
- make changes to service to apply tracing correctly
- Deploy changes as canary
- Add some resilience using service mesh (retry, timeout, etc)
- Debug service
- try with squash
- try with loop