Moving from a monolithic architecture to a service-based architecture may look like a daunting task. The good news is it does not need to be. A maturing cloud native tooling market is making it easier to get the job done.
In this webinar, Steve will cover the steps required to move a standard J2EE application from a monolithic architecture to a service based architecture. He will cover tools such as Ngnix, Docker, Kubernetes and DeployHub to manage and configure this new environment. Anyone with an interest in shifting to microservices will benefit from hearing this "roadmap" presentation.
2. DevOps Guru
Steve Taylor, CTO
Co-founder and creator of DeployHub and OpenMake Meister, Expert in builds, releases, Kubernetes and Service
Mesh.
3. Agenda
Walk through a Road Map for migrating a J2EE App to microservices.
Identify how your CI/CD Pipeline changes.
Talk about Domain Driven Design for Re-use.
5. Containers First
Baby Steps
A container provides an isolated context in
which an application, together with its
environment can run. Think of containers as
your new MSI (setup.exe).
Containers host both applicaitons and Services
in a Kubernetes environment.
6. Step 1
Containerize your Java App with Runtime
• The container should have one purpose
(entry point).
• The container should be self-contained.
9. Step 4
Build your Kubernetes Cluster
• Start with a Google and their free
credits. The wizard will help you
build your cluster.
• You will run a Command Line Client
install.
• Learn Helm.
10. Step 5
Start thinking Domains
• Domain Driven Design, a critical strategy in
managing reusable services (check out
microservices.io).
• Learn DeployHub Team to organize your
Domain structure and start cataloging
your services.
11. Step 6
Add a Binary Repo to your CI/CD process
• Start managing your binaries in a repo for
the container build step.
• Every Build will be stored with a version
number and critical for tracking History.
12. Step 7
Add a Docker (container) repository to your CI/CD
• Start managing your binaries in a repo for
the container build step.
• Every Build will be stored with a version
number, critical for tracking History.
13. Step 8
Auto Deploy via CI/CD
• Use DeployHub Team to Auto Deploy
• Track your configurations and version for
a single source of truth.
17. Changes in Your Pipeline
Building Containers not Code
New Steps:
Image Build and Container Registry
Less Compiling of code.
18. Changes in your Pipeline
Version and Configuration Management Shift
In Monolithic development, versioning and configuration
management is done at 'build-time.' Smaller pieces of
source code, less branching and merging, small builds (if
any).
In a microservice architecture these functions are shifted
to run-time. Linking is done via APIs.
19. This is NOT Easy
The Netflix Microservices Map or "Death Star"
Where are the Applications and what services do they consume?
21. And the Versions of Services
Application Versions and Microservice Versions
22. The Solution - DeployHub
SaaS based sharing and configuration management platform for microservices with
deployments
SaaS with Open Source Model
DeployHub Team Free (Currently over 70 users)
DeployHub Pro $208 per Month, Annual Subscription
Enterprise $75K, Annual Subscription
Ortelius Open Source Project
Ortelius.io
23. DeployHub is a Modern Configure and Deploy Solution
Catalog and publish using a Domain Driven Design Version and track Application to Services
configurations
Fast, Safe Independent Deployments
24. What DeployHub Does that is Hard
How We are Unique
Tracking applications to microservices and reusable components (web components, infrastructure, database).
25. Thank you and Questions
Learn More at:
DeployHub.com
Follow Us on Twitter @DeployHubProj
Follow me at @sbtaylor15
NM Thought Leadership Meetup on Zoom (CD.Foundation)
https://www.meetup.com/nm-cdf-Area-Meetup/