Kubernetes Design Patterns Training Course

Overview

The evolution of microservices and containers in recent years has significantly changed how we design, develop, deploy and run software. Modern applications must be optimized for scalability, elasticity, failure, and change. Driven by these new demands, modern architectures require a different set of patterns and practices. In this training, we examine ways to identify, understand and adjust to these new requirements.

Audience
This training is intended for people who are somewhat familiar with container technology and with Kubernetes concepts but are perhaps lacking the real world experience. It is based on use cases, and lessons learnt from real life projects with the intention of making people inspired to create and manage even better cloud native applications.

  • Developers
  • Operations
  • DevOps
  • QA Engineers
  • IT Project Managers

Format of the Course

  • Interactive lecture and discussion
  • Lots of exercises and practice
  • Handson implementation in a live-lab environment

Course Customization Options

  • To request a customized training for this course, please contact us to arrange.

 

Requirements

  • Familiarity with using the Linux command line, Linux file system, Linux networking, bash scripting.
  • An understanding of programming concepts and methodologies.
  • Familiarity with Docker and Linux containers technology.
  • Familiarity with Kubernetes concepts.

Course Outline

  • Introduction
  • Recap about Linux containers technology
  • Recap about Kubernetes basic concepts
  • Microservice based applications
  • The 12 Factors App Principles
  • Foundational Patterns: Distributed Primitives, Predictable Demands, Dynamic Placement, Declarative Deployment, Observable Interior, and Life Cycle Conformance.
  • Behavioral Patterns: Batch Jobs, Scheduled Jobs, Daemon Services, Singleton Services and Self Awareness.
  • Structural Patterns: Sidecar, Initializer, Ambassador, and Adapter.
  • Configuration Patterns: Env Var Configuration, Configuration Resources, Configuration Templates, and Immutable Configuration.
  • Summary and Conclusion

Leave a Reply

Your email address will not be published. Required fields are marked *