Microservices

Live Online (VILT) & Classroom Corporate Training Course

This Microservices Architecture training course teaches attendees how to design microservice-based systems for on-prem and cloud deployment.
LoadRunner Logo

How can we help you?

  • CloudLabs
    CloudLabs
  • Projects
    Projects
  • Assignments
    Assignments
  • 24x7 Support
    24x7 Support
  • Lifetime Access
    Lifetime Access
Box

Overview

This course helps participants learn the top microservices design patterns, how microservices integrate with containerized systems, strategies for integration with existing systems, and more.

Box

Objectives

At the end of Microservices training course, participants will be able to

  • Understand when to break up/not break up monolithic code when transitioning to microservices
  • Explore fundamentals of microservices architecture
  • Apply design patterns to ensure the optimal architecture
  • Manage APIs
  • Integrate microservices with existing systems
  • Ensure the stability/robustness of microservices
Box

Prerequisites

All students must know programming fundamentals and software design principles.

Box

Course Outline

  • 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

  • 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

  • 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

  • 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

  • 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 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

  • 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

  • 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

  • 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

  • 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
Box

Testimonials

Shamsudeen Bawa

Synergific Software Team has been very supportive, and working with them has been a best decision that we could ever made, They are just a call away. You guys are AWESOME, Thank You, Keep up the Good Work!!!

Shamsudeen Bawa

Vice President, J.P Morgan, CIS, USA

Farhan Hafiz

Synergific Software has been of great help and I plan to continue to use your services in the future for my business needs.

Farhan Hafiz

Data Architect, Fiserv

Dr. Sahdev Singh

I think Synergific Software is great. I liked that it was hassle free and easy to set up. Again, it's a great feature for a fast and cheap set up, which gives me peace of mind, as I know have a terms of use agreement.

Dr. Sahdev Singh

Under Secretary, Ministry of Law & Justice, Govt. of India

M Chikanna Swamy

I liked using Synergific Software very much. I thought the website was easy to navigate and the instructions for generating the terms was clear. I even recommended you on a Facebook Group I am a member of.

M Chikanna Swamy

Director & Learning Head, Mindtree