Discover how to accelerate the modernization of your Java Enterprise applications with no refactoring. Without re-architecting or re-writing, we will show you how to modernize painlessly to achieve faster time-to-market, simplified deployment and scaling, improved security, painless patching, and save money on infrastructure resources and licensing cost.

1. Modernizing Java EE with
Mesosphere DC/OS

2. Agenda
● Challenges of Java EE Modernization
● Introduction to Mesosphere DC/OS
● Demo
● Java EE with Mesosphere DC/OS
● Demo
● Mesosphere DC/OS vs Other Technologies
● Q&A

3. ● Cost:
○ Virtualization & application server licenses
○ Siloed underutilized infrastructure
● Operations
○ Weeks/Days to deploy, scale
○ Cost of management & troubleshooting
● Security
○ Slow patching of known vulnerabilities
○ Unprotected credentials
● Cloud Portability:
○ Moving to cloud requires lengthy migration
Maintaining Traditional Java EE Requires Significant Effort &
Budget

4. Application Landscape is Larger Than Greenfield Containers & Microservices
Properties:
• Microservices & Containers
• New languages, tools &
framework
Application Requirement
• Quick prototyping
• Cloud Portability
Properties:
• Mission Critical & Scale
• Monolithic
Application Requirements:
• Scale
• Security
• Reliability
• Quick fix
Properties:
• Old legacy technologies
• Retain data for regulatory
requirements
Application Requirements:
• Minimum investment to maintain
• Quick Patching
• Availability
New/Green FieldStableEnd-of-Life

5. Existing Modernization Approaches Require Lengthy Migration or Rewrite
Docker & Kubernetes
● Self Service, application
portability, efficiency
Pros
Cons
Platform-as-a-Service Public Cloud
● Unlimited Scalability
● Complementary services
● Significant Migration
effort & skill requirement
● Complexity of Integration
with existing on-premise
systems
● Skyrocketing cost
● Lockin
● Limited coverage of Java
EE application servers and
technologies
● Requires major change of
application development
lifecycle
● High cost and execution
risk
● New skill sets, modified
application development
process
● Rewrite or refactoring not
always technically or
economically feasible for all
applications
● Smooth developer
experience

6. Agenda
● Challenges of Java EE Modernization
● Introduction to Mesosphere DC/OS
● Demo
● Java EE with Mesosphere DC/OS
● Demo
● Q&A

7. Mesosphere DC/OS Automates and Pools Application Services
Across Hybrid Cloud Infrastructures
DC/OS Approach:
Datacenter-cloud as a single computer
1. Application-aware automation for complete lifecycle
automation of platform services
2. Workload pooling and density optimization for
dramatic cost savings
3. Unified hybrid cloud operations with high
availability, security, and multi-tenancy
Data
Analytics
Cluster
Message
Queue
Cluster
Data
Persistence
Cluster
Container
Orchestration
Cluster
CI/CD
Cluster
Traditional Approach:
Slow, Expensive, Hard
Data
Analytics
Message
Queue
Data
Persistence
Container
Orchestratio
n
Continuous
Integration
& Delivery
Datacenter-Cloud Operating System
7
1
2
3
● Manual & applications-specific configurations
are slow and difficult to maintain
● Cluster sprawl and low utilization
● High risk with unique “snowflake”
configurations in cloud or datacenter silos

8. Unified hybrid cloud operations
Securely manage cloud, datacenter, and edge
infrastructures from a single control plane
4
Unified Application Deployment on Any Infrastructure
Intelligent resource pooling
Optimize workload density for highest utilization with
resource guarantees
3
Broad workload coverage
Run today & tomorrow’s applications including traditional
J2EE, containers, analytics & ML
1
Application-aware automation
Automate workload-specific operating procedures to “as-a-
Service” anything from Kubernetes to data services
2

9. DC/OS simplifies
multi-cloud
operations to
running a single
resource pool

10. Over 100 platform
services accessible
with a single click
Examples include
production-ready
Kubernetes and a
rich set of
developer and data
services

11. DC/OS intelligent
resource pooling
runs multiple
distribute services
in a single
infrastructure

12. DC/OS unified
hybrid cloud
operations
intelligently places
workloads on
different cloud
regions
Availability zones
significantly
improve availability
of services

13. Unlock Hybrid Cloud Use Cases with Mesosphere DC/OS
● Minimize footprint at edge or
remote infrastructures
● Consistent operations across
clouds
● Deploy applications to multiple clouds
simultaneously
● Workloads automatically deployed
across fault domains (Racks or Cloud
Availability Zones)
Edge and Multi-Cloud Federation
● Easily add and remove cloud
capacity to on-premise clusters
Business Continuity & Disaster
Recovery
Cloud Bursting

14. Agenda
● Challenges of Java EE Modernization
● Introduction to Mesosphere DC/OS
● Demo
● Java EE with Mesosphere DC/OS
● Demo
● Q&A

15. Traditional Java EE Deployment & Challenges
Browsers
F
i
r
e
w
a
ll
F5/Router
Cluster
Instance 1
Cluster
Instance 2
Cluster
Instance n
DB
DB Cache
1.) Adding instances generally requires router changes
2.) No ability for auto-scale
1.) Resources rarely removed as volume demand
2.) Challenges adding new servers

16. Cluster
Instance 1
Java EE with Mesosphere DC/OS
Browsers
Firewall
F5/Router
Cluster
Instance 2
Cluster
Instance 3
DB
DB Cache
Router Points only to Public Agent. Marathon-LB handles the routing.
1.) App Owner can scale instances based on needs
2.) Auto-scaling capability to up and down scale instances based o
3.) Consistent deployments – no snow flakes
4.) BIN Packing saves on required resources
Edge-LBor
Marathon-LB 1.) Use integrated CI/CD tools such as Jenkins,
2.) Changes deployable without Application re
• Introduce perimeter security
• Manage sensitive resource passwords with secrets

17. Cloud
Portability
Java Enterprise with Mesosphere DC/OS
Reduction of
Infrastructure Cost
Improvement in Dev &
Ops Productivity.
With Faster Patching
and Password
protection
On Any Bare-Metal,
Virtual, or any Public
cloud
50% 300%
Better
Security

18. Running Java EE Apps with Mesosphere DC/OS Without Modification
Marathon:
● Single Interface for managing application lifecycle
with GUI/CLI/API
Apache Mesos:
● Abstracts data center resources (CPU, MEM, GPU,
network, storage) into one pool
● Offers & tracks resources to all workloads
● Restarts workloads on node or task failure
Universal Containers Runtime (UCR)
● Run any linux application OR Docker container
● Dynamically fetch application binaries
● Maintain security & resource isolation
Apache
Mesos
Marathon
Mesos Agent/UCR
JenkinsDocker
Weblogic Tomcat
Mesos Agent/UCR
JenkinsDocker
1
Weblogic Tomcat
2
3
1
2
3

19. Run your Java EE Apps on half the infrastructure with DC/OS
Virtualization Software
OS
App
OS
App
OS
App
OS
App
OS
App
OS
App
OS
App
OS
App App App App AppApp App App App
App App App AppApp App App App
Available Resources for Applications: < 45%
Example: 32 Core (2xCPU-16 Core), 128GB RAM
● Virtualization: 2 CPU-Cores & 8 GB RAM (%6)
● 8x VM OS: 16 CPU-Cores & 64 GB RAM (%50
Available Resources to Apps:
● 14 CPU-Core & 56GB RAM (44%)
Example: 32 Core (2xCPU-16 Core), 128GB RAM
● Operating System: 2 CPU-Cores & 8 GB RAM (%6)
● DC/OS : 2 CPU-Cores & 8 GB RAM (%6)
Available Resources to Apps:
● 28 Core & 112 GB of RAM (87.5%)
Available Resources for Applications: > 87%
Reduce Java EE infrastructure footprint by 50%

20. Increase DEV & OPS Productivity With Mesosphere DC/Os
Traditional Approach With Mesosphere DC/OS
Development:
● Manual Deployment or hard to manage
automation scripts
● Complex Integration with CI/CD tools
Operations:
● Days/Weeks to deploy or patch
applications
● Manual Scaling,
● Manual Instrumentation per cloud
Development:
● Self Service Infrastructure
● Simple Integration with CI/CD
● Consistent deployment for all applications
Operations:
● Deploy in minutes
● Automated Scaling, Blue/Green Deployment
● Integrated Health checks
● Automatic detection and restart on
application and node failure

21. Improve Java EE Application Security
Faster Patching
● Deploy and patch applications across the entire
organization in minutes
Protect Password & Sensitive Files
● Integrated Secrets Management
● Integrated RBAC
● Secrets encrypted at communication and rest
● Dynamically load secrets on application
launcher, scale
DC/OS Secret Store
(Highly available,Encrypted at Rest)
Application
Instance 1
Application
Instance 2
Encrypted in
Transport

22. Automatically
deploy workloads
to different clouds
regions and zones

23. Deploying Applications with Mesosphere DC/OS UI

24. Running Java EE with Mesosphere DC/OS

25. Deploying Applications with Mesosphere DC/OS CLI
$ dcos Marathon app add app.json
1- Define app resource
requirements 2- Fetch Jetty server,
application war, JRE
3- Define Networking
(Ports, LB)
app.json
4- Execute App
Standard Linux
Commands

26. Agenda
● Challenges of Java EE Modernization
● Introduction to Mesosphere DC/OS
● Demo
● Java EE with Mesosphere DC/OS
● Demo
● Q&A

27. RHEL required for public cloud,
bare-metal or VM
No data services portability
No hybrid, multi, or edge-cloud
support
Mesosphere DC/OS vs. Other Technologies
Broad Workload
Coverage
Application-Aware
Automation
Hybrid Cloud
Operations
Intelligent
Resource Pooling
Mesosphere DC/OS Red Hat OpenShift Pivotal (PCF/PKS) Amazon AWS
Runs only K8s (Docker) & JBoss
apps w/proprietary interface
No support for production data
services (dev/test only)
Runs K8s (Docker), legacy apps
(Java EE, C++), data services & dev
tools such as Spark, Kafka,
Cassandra, Elastic, TensorFlow,
etc.
Production services with OSS &
commercial support options
Cloud Foundry for (limited) legacy
apps, PKS (K8s) for Docker
Limited support for production
data services (dev/test only)
except proprietary (Gemfire &
Greenplum)
Runs K8S, Docker, legacy
apps (Java EE, C++), data
services & dev tools
Advanced services have
proprietary interfaces (e.g.,
Lambda, Kinesis,
DynamoDB)
Lifecycle management limited to
stateless apps only
Lifecycle management limited to
stateless apps only
Similar to DC/OS with
additional cost
Workload-specific automation for
cloud-like experience including
install, upgrade, scale & failure
recovery
Siloed clusters for containers,
legacy apps & data services,
lowering utilization & driving up
cost
Siloed cluster for PCF, PKS & data
services, lowering utilization &
driving up cost
Dedicated cluster for each
service, lowering utilization
and driving up cost
Proprietary AWS services
cause cloud lock-in
No data services portability
No on-premise, hybrid, multi,
or edge-cloud support
VMware only on-premise, options
for public cloud
No data services portability
No hybrid, multi, or edge-cloud
support
Cloud portability across any public
cloud, bare-metal or VM; enabling
edge computing, cloud bursting &
BC/DR
One infrastructure pool securely
shared across apps and data
services, increasing utilization,
reducing cost

28. Q&A

29. Switch between
linked DC/OS
clusters using a
consistent
operating
experience

30. Multiple
organizations or
functions can
securely share a
single DC/OS
cluster