MuleSoft Meetup: Mule 3 to 4 Migration & Runtime Fabric

May 27th 2019 : 3 to 4 Migration & Runtime Fabric
Singapore MuleSoft Meetup #2

All contents © MuleSoft Inc.
Our Partners
2

Agenda
4
• 6:30 pm: Registration, arrivals, food and drink
• 7:00 pm: Introduction
• 7:15 pm: Mule 3 to 4 Migration
• 7:40 pm: Runtime Fabric
• 8:00 pm: Q&A
• 8:10 pm: Networking

Organizers
6
Julian Douch - Managing Director
WhiteSky Labs
Integration veteran of 20 years, transformation strategist, and digital leader, and now leading
WhiteSky Labs expansion into ASEAN.
Having established it's newest office in APAC here in Singapore, I'm now driving fast to
similarly establish the MuleSoft community also, forging relationships with the current
developer community, expanding the community by reaching new technologists who've a
passion for building out a new API-centric digital economy.

Speaker
7
Rika Ng - Senior Solutions Engineer
MuleSoft
Rika is a Lead Solution Engineer with MuleSoft, helping Asia customers and
partners on their customer experience and digital transformation journey with the
help of APIs and integrations. Rika brings over 20 years of experience in technology
and enterprise software, and has worked with mission-critical systems across
several industries.

Speaker
8
Ryan Andal – Senior Integration Consultant
WhiteSky Labs
MuleSoft Ambassador, Meetup Leader, Forum Moderator
Ryan is a MuleSoft Ambassador, Meetup Leader (Manila PH), Forum Moderator and a
Senior Integration Solutions Consultant with 6 years of experience in analysis, design and
development. He has worked across many industries including insurance, e-commerce,
taxation, financial management, human capital management, government, manufacturing,
inventory, shipping and logistics.

Ryan Andal
MuleSoft Ambassador
Senior Integration Consultant, WhiteSky Labs
Mule 3 to Mule 4 Migration

Agenda
10
• Benefits of Migrating to Mule 4
• Mule Migration Assistant
• Migration Challenges
• Migration Options
• When to upgrade?
• How to prepare for migration?
• Execution
• Getting ready to deploy
• Transition
• Case Study – ALH Group

Benefits of Migrating to Mule 4
11
• Extended support
• Mule 4 is more than 1.5 year in the market and has a stable version
• Mule 4 documentation is available and the support in MuleSoft Community is growing
• Easier to use
• Better processing of large data
• Runtime runs at its best without manual tuning
• Reduced long-term maintenance costs by simplifying operations and upgrades
• Reduced management complexity allow users to speed up the on-ramping process and deliver
applications faster

Mule Migration Assistant
12
About the Mule Migration Assistant
• Convert Mule 3 project zips to equivalent Mule 4 project jars using the Utility
• Currently in beta testing with delivery partners
Steps:
• Create a Mule 4 App from the Mule 3 App using mule migration assistant runner
• Import the Migrated App to Studio 7
• Perform Manual Migration Procedures

13

Converted Mule 4 applications still need
manual effort to verify and/or tweak

Migration Challenges
15
Do not underestimate changes
• Migration will be difficult if you are not following Mule development best practices
• Migration of large amount of Java and script can be challenging
• Some modules are not backward compatible
• Migrating custom connectors (Devkit Connector) to Mule SDK
• For people experienced in Mule 3, the firsts steps in Mule 4 can be difficult
– Deprecation of ‘Mule Expression Language’ (MEL)
– Mule Message Properties/Variables
– New and updated syntax for DataWeave 2
– Updated testing framework to MUnit 2

Migration Options
16
Comparison
Mule Migration Assistant Manual Migration
Not yet available You can implement anytime
Requires knowledge with migration changes and
expertise in Mule 4
Requires expertise in Mule 3 and Mule 4
Automated base project and manual effort From the scratch project and manual effort
Code refactoring and re-writing Code re-writing
If you don’t have a good code implementation –
it will copy the same code
Easy to enhance the code

When to upgrade?
17
Should you start the journey now?
• The Mule version you are using reaches end of support or end of life
• You want to make significant updates to the existing applications
• You want to take advantage of key Mule 4 capabilities
• You decide to upgrade all your apps to Mule 4 so that they are on one version
• Customers are already successfully deploying new applications in Mule 4

How to prepare for migration?
18
Understand the scope
• Start by collating a list of Applications and flows in
a spreadsheet or tool and capture relevant
metrics to calculate effort
Impact Assessment
• Assess each API complexity
• Is it full rewrite, small or large modification?
Determine method / cut-over
• Cut-over approach / migration plan
• Test Driven Approach
• Identify value of Mule Migration Assistant
Identify Dependencies
• Production Samples for Unit Testing
• Documentation, RAML, Wikis, access to
Application SMEs
• People Dependencies
• Third Party Extensions for Logging etc
• Produce a dependency register with due dates
and who responsible
Who should be involved?
• MuleSoft Customer Success Team
• Application Subject Matter Experts
• Quality Assurance
• Implementation Partner

Execution
19
Use an Agile Delivery Method
• Organize Application conversions in Sprint cycles
• Start with a simple Application first to prove out
your Development, Test, and Transition processes
• When confident in your process start tackling
more complex Applications – Don’t leave the
hardest ones until last!
Mobilize the right team
• Does your internal team have the necessary skills
to begin building on Mule 4 right away?
• Internally or in collaboration with a partner – Kick-
start or deliver the whole upgrade?
• How much work can be done by off-shore
resources for commercial benefit?

Getting Ready to Deploy
20

Transition
21
Produce a transition plan
• Sprint Migration – Deploy APIs when ready
• Post Go-live Verification Testing
• Identify Pre and Post deployment tasks well
before deployment
• Can you do a rehearsal ahead of time?
• Do all cut-over stakeholders understand their
roles
Licensing
• Talk to your MuleSoft Account Executive or a
MuleSoft Services Partner about transitional
licensing requirements

Case Study ALH Group
22
Why
• Getting ready to use the MuleSoft Platform for innovative API
offerings in 2019
• Moving from Mule ESB Batch / Point to Point approach to a modern
API Led Architecture
• Opportunity to learn MuleSoft Design best practices
Scope
• Mix of 12 simple to complex Applications
• Decided not to wait for the Mule Migration Assistant as existing
Applications had a high amount of custom code and scripts.
Collaborative Team
• The ALH Development Lead worked closely with WSL to plan and
deliver the upgrade.
• WSL kicked off the first Application migrations with shadowing from
the ALH Team.
• The ALH team were able to complete the last 4 Application migrations
• Utilized off-shore development capability after first sprint cycle was
successful
• Successful transition!
• “I am enjoying the new Mule components
in Version 4. In particular, the simplified
File and Database components
• The profile of MuleSoft has increased here
at ALH. MuleSoft has provided an
opportunity to start thinking about
leveraging all data in the organization
• With the assistance of WSL, ALH is
confident to move forward with MuleSoft.
We are tackling projects that were
considered too challenging some time
ago.”
• Chris Minas – ALH Group MuleSoft Lead
Developer

References
23
• End of life support: https://www.mulesoft.com/legal/versioning-back-support-
policy#datebasedversioning
• Mule 4 for Mule 3 Users: https://docs.mulesoft.com/mule-runtime/4.2/index-migration
• Mule Migration Assistant: https://beta.docs.stgx.mulesoft.com/beta-mule-migration-tool/mule-
runtime/4.1/migration-tutorial
• Mule Migration Assistant Procedures: https://beta.docs.stgx.mulesoft.com/beta-mule-migration-
tool/mule-runtime/4.1/migration-tutorial#step_3
• Migrating Connectors: https://docs.mulesoft.com/mule-runtime/4.2/migration-connectors
• Migration Preparation: https://docs.mulesoft.com/mule-runtime/4.2/migration-prep
• What's new with Mule 4 whitepaper: https://www.mulesoft.com/whitepaper/api/what-is-new-mule-4
• MuleSoft Meetup presented by Nick Bowman, Consulting Manager for WhiteSky Labs

MuleSoft Runtime Fabric
Rika Ng
Senior Solutions Engineer, MuleSoft

Anypoint Runtime Fabric – What is it?
27
Overview
Runtime Fabric (RTF) orchestrates and
automates the deployment of Mule runtimes
into containers in any cloud or on-premises.
Benefits
• Deploy consistently across any cloud (Azure &
AWS) or data center
• Run multiple runtime versions in the same
Runtime Fabric
• Scale horizontally and redeploy w/ zero-
downtime
• Easily manage via the control plane hosted by
MuleSoft
• No resources required to support or maintain
orchestration & automation
27
CUSTOMER’S NETWORK
Server Server Server
Mule
App
Mule
App
Mule
App
Runtime Fabric services
Mule
App
Mule
App
Mule
App
Mule
App
Mule
App
Mule
App
Anypoint Runtime Fabric
Control plane
Docker & Kubernetes

Why should existing MuleSoft customers care?
Deploy and manage runtimes
across clouds
● ‘CloudHub Like’ experience,
wherever they choose
● Reap the benefits of
container orchestration with zero
work
● Guaranteed future mule
capabilities
● Default vehicle for Anypoint
Security

The journey so far...
August 2018
Launch of GA ramp for Runtime
Fabric with high touch
engagements
End of high touch engagements,
GA ramp with self serve
December
2019
Shipped 9
improvements identified
during GA ramp
February 2019
Anypoint Monitoring,
Anypoint Visualizer
support
April
2019

Increase number of apps per OS,
Optimize or displace VMs, Reduce # of
servers (incl. maintenance & licensing)
Hardware
Host OS
Container Engine
App 3
App 2
App 1
App 6
App 5
App 4
App 9
App 8
App 7
App 12
App 11
App 10
Container Model
Low utilization, inefficient,
costly, unnecessary
Hardware
Traditional IT Model
Hypervisor
VM 4VM 3VM 2VM 1
App 4
Guest OS
App 3
Guest OS
App 2
Guest OS
App 1
Guest OS
WASTEDWASTEDWASTEDWASTED
Containerization for scale & ops efficiency

Container Platforms Search Interest

Kubernetes is the Kernel of Container Management
Kubernetes
App
Marketplace
Infrastructure
Automation
Logging
Configuration
Management
Service
Broker
App Telemetry
Notification
Services
Installation,
maintenance, and
management
Storage
Ingress and LB
Tracing
CI/CD
Policy Control

DIY Production-ready Kubernetes is limited
1. Manual installation - “The hard way”
– The user downloads all components on each node, creates config files, etc.
– Easy to get things wrong
2. Configuration management (ansible, chef, puppet, etc.)
– Lots of assumptions made
– Some only work with specific cloud providers
– Some expect internet connectivity
3. “Easy Button”
– sig-cluster-lifecycle focused on creating production-ready Kubernetes cluster creation
– Just GA in Dec 2018, sans non critical add-ons e.g. monitoring, logging, cloud provider
integrations

Runtime Fabric vs In-House K8s/Docker
Fully supported configuration
with tested patch to mitigate
operation risk
Customer managed
configuration with numerous
and individual patches to
handle
Runtime Fabric K8s + Docker
Built-in HA and autoscaling
capabilities
Customized HA and scaling
scenario to implement
Anypoint Edge / Tokenization
Ready for higher security
(DDos, Data Masking…)
Not applicable / DIY
Subscribe for the Cores you
need, independently from the
underlying hardware
configuration
Potentially subscribe to all the
Cores used in the Docker
farm, as there’s no way to
isolate the size of the
container
Support
Operations
Security
Cost

Anypoint Platform – Control vs Runtime Plane
Mule runtime engine
Control plane
Runtime plane
Design
Anypoint Design Center
Secure
Anypoint Security
Engage
Anypoint Exchange
Manage
Anypoint Management Center
Run
Mule

Runtime Fabric – Control vs Runtime Plane
CloudHub
On-prem
(naked mules) Anypoint Runtime Fabric
Deployed:
Cloud
Deployed:
On-prem/
private IaaS
Managed by
Managed by
MuleSoft MuleSoft
Customer Appliance: MuleSoft
Infrastructure: Customer
MuleSoft
Anypoint Platform - Private
Cloud Edition
MuleSoft
Customer

Runtime Plane - Controllers vs Workers
Controller nodes
Worker nodes

Runtime Plane – Hardware (Development)
Minimum of 1 controller VM to operate Runtime Fabric; maximum of 5.
• 2 cores each minimum
• 15 GiB memory minimum
• 80 GiB dedicated disk for the operating system.
• 60 GiB dedicated disk with 3000 provisioned IOPS for etcd.
• 100 GiB dedicated disk with 1000 provisioned IOPS for Docker.
Minimum of 2 worker VMs to run Mule applications and API gateways; maximum of
16.
• 2 cores each minimum.
• 15 GiB memory minimum.

Runtime Plane – Hardware (Production)
Minimum of 3 controller VMs to operate Runtime Fabric; maximum of 5.
• 60 GiB dedicated disk with 3000 provisioned IOPS for etcd.
Minimum of 3 worker VMs to run Mule applications and API gateways; maximum of
16.

Runtime Plane – Other Considerations
• Operating systems
– Red Hat (RHEL) v7.4, v7.5, v7.6
– CentOS v7.4, v7.5, v7.6
• Additional resources required includes:
– External load balancer if incoming traffic is enabled to Runtime Fabric
e.g. TCP load balancer with server pool to each of the controller VMs
– At least one additional worker VM (including hard disks) for rolling upgrades
and operating system level patches

Anypoint Runtime Fabric – how to get it?
• Available to all existing MuleSoft customers with Platinum
subscription
• For evaluators with trial accounts
– Get an Anypoint Platform account
– Email info@mulesoft.com to turn on additional entitlement
• Or … talk to a MuleSoft partner. J

Permissions assigned

Runtime Fabric binaries

So how do clients deploy a fabric?
47
○ Terraform template
○ Easy to modify:
■ VPC
■ Instance types
■ # controllers and
workers
■ Base AMI
○ ARM templates
○ Easy to modify:
■ Virtual network
address
■ Subnet address
○ Detailed Manual
Installation Guide
○ Specific system &
network
requirements

Installation Steps
1. Provision the infrastructure based on the system, disk and network
requirements
– AWS
– Azure
– VMs / Bare Metal
2. Follow the manual or scripted installation based on the target
platform
3. Associate the Business Group / Environment for Runtime Fabric
deployments

Installation Steps (cont.)
4. Enable the inbound traffic to Runtime Fabric
5. Configure logs in Runtime Fabric
6. Configure alerts in Runtime Fabric
7. Deploy a sample application to Runtime Fabric

Deploy a sample application to Runtime Fabric

It’s not that complicated …

Training is available!
Training and Certification
https://training.mulesoft.com/instructor-led-training/apops-rtf

For more information…
Runtime Fabric
https://docs.mulesoft.com/runtime-fabric/latest/

What’s next – MuleSoft U & Training

What’s next – Anypoint MuleSoft Webinar

What’s next – 5th September 2019
• 6:30 pm: Registration, arrivals, food and drink
• 7:00 pm: Introduction
• 7:15 pm: TBC
• 7:40 pm: TBC
• 8:00 pm: Q&A
• 8:10 pm: Networking

Picture Time
61
…. And don’t forget to grab some swag!

Networking time
Introduce yourself to your neighbors!

See you next time
Please send topic suggestions to the organizer

MuleSoft Meetup: Mule 3 to 4 Migration & Runtime Fabric

MuleSoft Meetup: Mule 3 to 4 Migration & Runtime Fabric

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to MuleSoft Meetup: Mule 3 to 4 Migration & Runtime Fabric

Similar to MuleSoft Meetup: Mule 3 to 4 Migration & Runtime Fabric (20)

Recently uploaded

Recently uploaded (20)

MuleSoft Meetup: Mule 3 to 4 Migration & Runtime Fabric