Mastering the Mesh: A Comprehensive Guide to Linkerd 2 Service Mesh
- 1 min
Mastering the Mesh: A Comprehensive Guide to Linkerd 2 Service Mesh
This course is designed to teach you everything you need to know about Linkerd 2, a Service Mesh that provides a way to control and monitor the communication between services in a microservices architecture.
What you will learn
- What is a Service Mesh?
- What are the benefits of using a Service Mesh?
- How Linkerd 2 works?
- How to install and configure Linkerd 2
- How to use Linkerd 2 to control the communication between services
- Service discovery: Finds services without having to hardcode IP addresses or DNS names.
- Load balancing: Spreads traffic across all instances of a service.
- Fault injection: Simulates failures to test reliability.
- How to use Linkerd 2 to improve ovservability, reliability, and security of microservices applications
- Metrics and tracing: Monitors traffic and behavior.
- Security: Protects from attacks with features like mTLS and authentication.
- Retries: Attempts to reconnect to a service that has failed.
- Timeouts: Prevents requests from hanging indefinitely.
Who is this course for?
This course is for anyone who wants to learn about Linkerd 2. This includes:
- Developers who are building microservices applications
- DevOps engineers who are responsible for deploying and managing microservices applications
- Site reliability engineers who are responsible for monitoring and troubleshooting microservices applications
What you will get
- Live lectures and Q&A sessions with an expert instructor
- A comprehensive course syllabus that includes all the topics that will be covered in the course
- A certificate of completion that you can use to demonstrate your skills and knowledge
Enroll today and start learning about Linkerd 2!
Use a preferred way to book a training session:
Who am I?
Check out my about page.
Languages
This course is available in both 🇬🇧English and 🇵🇱Polish.
Krzysztof Słonka
Software engineer at Kong. Pragmatic programmer. Nowadays I mostly write "if err != nil"