The cost of a mesh
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
count what a mesh costs before adopting it.
Planned topics
- Costs: latency per hop, CPU and memory, upgrade effort, debugging a new layer, on-call skills.
- Alternatives: libraries, an API gateway, plain TLS with a cert manager.
- Adopt for a named benefit, measured in a trial.
- Reject when the problem is process, not technology.
Draft outline details
Demonstration
a decision matrix: needs (mTLS everywhere, canary, polyglot telemetry) versus options (mesh, libraries, gateway) with cost estimates.
Check your understanding
When reject a mesh?
Show answer
When the problem is process rather than missing technology.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.