Microservices Architecture Training

This Microservices Architecture Training course teaches attendees how to design Microservices-based systems for on-prem and cloud deployment. Students learn the top Microservices design patterns, how Microservices integrate with containerized systems, strategies for integration with existing systems, and more.

Attendees will not need to install any software on their computers for this class. The class will be conducted in a remote environment that ENO Institute will provide; students will only need a local computer with a web browser and a stable Internet connection. Any recent version of Microsoft Edge, Mozilla Firefox, or Google Chrome will be fine.

For classes delivered online, all participants need either dual monitors or a separate device logged into the online session so that they can do their work on one screen and watch the instructor on the other. A separate computer connected to a projector or large-screen TV would be another way for students to see the instructor’s screen simultaneously with working on their own.

Microservices Architecture Training Materials

• All Microservices Architecture training students receive comprehensive courseware.
• Software Needed on Each Student PC

• Architecting Security Training
• Applied Systems Engineering Training
• Architecting with DODAF Training
• Certified Systems Engineering Professional Training (CSEP)
• Combat Systems Engineering Training

Introduction

Breaking Up Monoliths – Pros and Cons

• Traditional Monolithic Applications and Their Place b)  Disadvantages of Monoliths
• Developer’s Woes
• Architecture Modernization
• Architecture Modernization Challenges
• Microservices Architecture is Not a Silver Bullet!
• What May Help?
• In-Class Discussion

Microservices

• What is “Microservices”?
• Unix Analogy
• Principles of Microservices
• Services within an SOA vs Microservices e)  Properties and Attributes of Microservices f)   Benefits of Using Microservices
• The Two-Pizza Teams
• Beware of Microservices Cons i)   Anti-Pattern: Nanoservices
• The Twelve-Factor App Methodology k)  The Select Factors
• Serverless Computing
• Microservices – Operational Aspects
• Microservices Architecture Training

Microservices Architecture Defined

• The Microservices Architecture
• SOA Promises and Expectations
• Microservices Architecture vs SOA
• The ESB Connection
• Microservices Architecture Benefits
• Microservices Architecture Choices and Attributes g)  Example: On-Line Banking Solution Based on MsA h)  Distributed Computing Challenges
• Replaceable Component Architecture j)   The Actor Model
• MapReduce Distributed Computing Framework
• Hadoop’s MapReduce Word Count Job Example
• What Can Make a Microservices Architecture Brittle?
• 4+1 Architectural View Model

Containerization Systems for Microservices

• Infrastructure as Code
• Why Not Just Deploy My Code Manually?
• What is Docker
• Docker Containers vs Traditional Virtualization e)  Docker is a Platform-as-a-Service
• Docker Integration g)  Docker Services
• Docker Application Container Public Repository i)           Container Registries
• Your Own Docker Image Registry
• Starting, Inspecting, and Stopping Docker Containers l)   One Process per Container
• The Dockerfile n)  Kubernetes
• What is OpenShift

Commonly Used Patterns

• Why Use Patterns?
• Performance-Related Patterns
• More Performance-Related Patterns
• Pagination vs. Infinite Scrolling – UX Lazy Loading e)  Integration Patterns
• More Integration Patterns
• The Service Mesh Integration Pattern h)  Mesh Pros and Cons
• Service-to-Service Communication with Mesh j)       Resilience-Related Patterns
• Microservices Architecture Training
• Summary

API Management

• API Management Defined
• The Traditional Point-to-point Integration Example c)  It Raises Some Questions …
• The Facade Design Pattern
• API Management Conceptual Diagram
• Complimentary Services for Microservices g)  What Else is Needed?
• The Driving Forces
• API Management Offerings
•  The Mashery API Management System Overview
• k)  AWS API Gateway Call Flow

Designing and Implementing Microservices

• Two Types of IT Projects
• What is In Scope of a Robust Microservices Design? c)  Scoping Your Microservices via the Bounded Context d)  Scoping Your Solution’s Microservices Architecture
• External / Shared and Internal Service Models
• General Architectural and Software Process Organizational Principles
•  Loose Coupling, the OOD Perspective
• Crossing Process Boundary is Expensive!
• Cross-Cutting Concerns
• More Cross-Cutting Concerns
• To Centralize or Decentralize Client Access?
• Decentralized Client Access m) Centralized Client Access
• The Facade Pattern
• The Facade Service Conceptual Diagram p)  The Naked Objects Architectural Pattern q)  When to Use Naked Objects Pattern
• Dealing with the State
• How Can I Maintain State?
• Micro Front-ends (a.k.a. MicroUI)
• How can MicroUI Help Me?
• Your Clients Are Diverse
• The “Rich Client” – “Thin Server” Paradigm
• The “Rich Client” – “Thin Server” Architecture
• RIA is a Driving Force to Turn the “Thin Server” into a Set of
• Microservices Architecture Training

Microservices

• z)  Design for Failure aa)Managing Failures Effectively
• bb)The Immutable Infrastructure Principle cc) Implementing Microservices
• dd)JAX-RS
• ee)Microservices-Oriented Application Frameworks and Platforms ff)  Embedding Databases
• gg)Embedded Java Databases

Microservices Integration

• One Common Observation
• The “One Service – One Host” Deployment c)  Things to Consider when Integrating
• Technology Options
• The Data Exchange Interoperability Options f)   The Correlation ID
• Enterprise Integration Patterns h)  Asynchronous Communication
• Benefits of Message-Oriented Middleware (MOM)
• Asynchronous Communication Models k)  Message Brokers
• A Message Broker Diagram
•  Asynchronous Message Consumption Patterns n)  Popular Messaging Systems
• Challenges of Managing Microservices p)  Options for Managing Microservices

1. q)  In-Class Discussion

Working with Data in Microservices a)  Monolithic Databases

• The Traditional Two-phase Commit (2PC) Protocol c)  Table Sharding and Partitioning
• The CAP Theorem
• Mechanisms to Guarantee a Single CAP Property f)   The CAP Triangle
• Eventual Consistency
• Handling Transactions in Microservices Architecture i)   The Event-Driven Data Sharing Diagram
• The Saga Pattern
• The Saga Log and Execution Coordinator l)   The Saga Happy Path
• A Saga Compensatory Request Example n)  In-Class Discussion
• The Need for Micro Databases
• Migrating Data from Existing Databases (Breaking up the Monolith

Database)

• One Data Migration Approach
• One Data Migration Approach (Cont’d)
• In-Class Discussion
• Command Query Responsibility Segregation (CQRS)
• The CQRS Communications Diagram v)  A Word of Caution
• The Event Sourcing Pattern x)  Event Sourcing Example
• Applying Efficiencies to Event Sourcing

Robust Microservices

• What Can Make a Microservices Architecture Brittle?
• Making it Resilient – Mechanisms
• Techniques and Patterns for Making Your Microservices Robust d) Fail Fast or Quiesce?
• Synchronous Communication Timeouts / Retries
• Asynchronous Communication Timeouts / Retries g) In-Class Discussion
• The Circuit Breaker Pattern
• The Circuit Breaker Pattern Diagram j) The Bulkhead Pattern
• Factor IX of the 12 App Methodology l)Feature Enablement
• Designing for Test and Failure n) Making Microservices Testable o)  Test for Failure
• Continuous Testing and Integration
• Continuous Release and Deployment r) SLAs
• Where and What to Monitor t) Logging and Monitoring

Conclusion

Microservices Architecture Training Course Recap, Q/A, and Evaluations