Flash Sale: Save 15% on IT Training

closeClose

Microservices Architecture Training

  • Contact Us For Pricing
  • Reviews star_rate star_rate star_rate star_rate star_half 1444 Ratings
  • Course Code ACCEL-MICRO-ARCH
  • Duration 2 days
  • Available Formats Classroom

This Microservices Architecture training course teaches attendees how to design, develop, and integrate Microservices. Students also learn about Monoliths and common design patterns.

Skills Gained

All students will:

  • Understand Monolith versus Microservices Design
  • Use Databases with Microservices
  • Use the Event Sourcing Pattern
  • Work with data in Microservices

Prerequisites

All students must know programming fundamentals and software design principles.

Course Details

Software Requirements

  • At least 8GB RAM (12GB or more preferred) with virtualization extensions enabled in the BIOS
  • VMware Workstation Pro or Workstation Player (Windows) or VMware Fusion (Mac)
  • At least 80GB free hard drive space
  • Virtual machine image that Accelebrate provides
  • Internet access

Microservices Architecture Training Outline

Introduction

Breaking Up Monoliths – Pros and Cons

  • Traditional Monolithic Applications and Their Place
  • 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 a "Microservice"?
  • Unix Analogy
  • Principles of Microservices
  • Services within an SOA vs Microservices
  • Properties and Attributes of Microservices
  • Benefits of Using Microservices
  • The Two-Pizza Teams
  • Beware of Microservices Cons
  • Anti-Pattern: Nanoservices
  • The Twelve-Factor App Methodology
  • The Select Factors
  • Serverless Computing
  • Microservices – Operational Aspects

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
  • Example: On-Line Banking Solution Based on MsA
  • Distributed Computing Challenges
  • Replaceable Component Architecture
  • 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
  • Docker is a Platform-as-a-Service
  • Docker Integration
  • Docker Services
  • Docker Application Container Public Repository
  • Container Registries
  • Your Own Docker Image Registry
  • Starting, Inspecting, and Stopping Docker Containers
  • One Process per Container
  • The Dockerfile
  • Kubernetes
  • What is OpenShift

Commonly Used Patterns

  • Why Use Patterns?
  • Performance-Related Patterns
  • More Performance-Related Patterns
  • Pagination vs. Infinite Scrolling - UX Lazy Loading
  • Integration Patterns
  • More Integration Patterns
  • The Service Mesh Integration Pattern
  • Mesh Pros and Cons
  • Service-to-Service Communication with Mesh
  • Resilience-Related Patterns
  • Summary

API Management

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

Designing and Implementing Microservices

  • Two Types of IT Projects
  • What is In Scope for a Robust Microservices Design?
  • Scoping Your Microservice via the Bounded Context
  • 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
  • Centralized Client Access
  • The Facade Pattern
  • The Facade Service Conceptual Diagram
  • The Naked Objects Architectural Pattern
  • 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 as a Driving Force to Turn the "Thin Server" into a Set of Microservices
  • Design for Failure
  • Managing Failures Effectively
  • The Immutable Infrastructure Principle
  • Implementing Microservices
  • JAX-RS
  • Microservice-Oriented Application Frameworks and Platforms
  • Embedding Databases
  • Embedded Java Databases

Microservices Integration

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

Working with Data in Microservices

  • Monolithic Databases
  • The Traditional Two-phase Commit (2PC) Protocol
  • Table Sharding and Partitioning
  • The CAP Theorem
  • Mechanisms to Guarantee a Single CAP Property
  • The CAP Triangle
  • Eventual Consistency
  • Handling Transactions in Microservices Architecture
  • The Event-Driven Data Sharing Diagram
  • The Saga Pattern
  • The Saga Log and Execution Coordinator
  • The Saga Happy Path
  • A Saga Compensatory Request Example
  • 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
  • A Word of Caution
  • The Event Sourcing Pattern
  • 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
  • Fail Fast or Quiesce?
  • Synchronous Communication Timeouts / Retries
  • Asynchronous Communication Timeouts / Retries
  • In-Class Discussion
  • The Circuit Breaker Pattern
  • The Circuit Breaker Pattern Diagram
  • The Bulkhead Pattern
  • Factor IX of the 12 App Methodology
  • Feature Enablement
  • Designing for Test and Failure
  • Making Microservices Testable
  • Test for Failure
  • Continuous Testing and Integration
  • Continuous Release and Deployment
  • SLAs
  • Where and What to Monitor
  • Logging and Monitoring

Conclusion

When does class start/end?

Classes begin promptly at 9:00 am, and typically end at 5:00 pm.

Does the course schedule include a Lunchbreak?

Lunch is normally an hour long and begins at noon. Coffee, tea, hot chocolate and juice are available all day in the kitchen. Fruit, muffins and bagels are served each morning. There are numerous restaurants near each of our centers, and some popular ones are indicated on the Area Map in the Student Welcome Handbooks - these can be picked up in the lobby or requested from one of our ExitCertified staff.

How can someone reach me during class?

If someone should need to contact you while you are in class, please have them call the center telephone number and leave a message with the receptionist.

What languages are used to deliver training?

Most courses are conducted in English, unless otherwise specified. Some courses will have the word "FRENCH" marked in red beside the scheduled date(s) indicating the language of instruction.

What does GTR stand for?

GTR stands for Guaranteed to Run; if you see a course with this status, it means this event is confirmed to run. View our GTR page to see our full list of Guaranteed to Run courses.

Does ExitCertified deliver group training?

Yes, we provide training for groups, individuals and private on sites. View our group training page for more information.

Does ExitCertified deliver group training?

Yes, we provide training for groups, individuals, and private on sites. View our group training page for more information.

Very good company, excellent course offerings and nice staff both admin and course instructors. Keep it up!

I enjoyed this class and the instructor did a very good job explaining the course material.

I am very satisfied with the course and teacher(Bill), and with the given option I will play with labs more after the class is over. Thank you

The entire AWS Essentials Course was great! ExitCertified supplied everything we need ahead of time and all went smoothly.

Thank you for training on AWS development. Course was good and encouraging but labs need to be improved and provide more information and ask students to more work than provide solutions.

0 options available

There are currently no scheduled dates for this course. If you are interested in this course, request a course date with the links above. We can also contact you when the course is scheduled in your area.

Contact Us 1-800-803-3948
Contact Us Live Chat
FAQ Get immediate answers to our most frequently asked qestions. View FAQs arrow_forward