-MuleSoft Latest Product Updates -Demo on VPC, VPN, DLB, and SLB

1. [01st August 2020]: [Deep Dive with Demo on Virtual
Private Cloud, AnyPoint VPN, Dedicated Load Balancer,
Cloudhub, Shared Load Balancer in MuleSoft]
[Mumbai - India]

2. All contents © MuleSoft Inc. 2
• 1.Please keep yourself muted unless you have any question.
• 2.We encourage keeping your video for making our meetup
interactive.
• 3.You'll can also write down your questions in chat section.
• 4.Once you join write down your registered name in chat section so
we will have an attendance.
• 5.As this is our first online Meetup, we appreciate your valuable
feedback. Thanks.
Guidelines for Mumbai MuleSoft Meetup #12 [Virtual]

3. All contents © MuleSoft Inc.
Agenda
3
 Introductions
 Important Announcements and Latest Releases
 Meet our Ambassadors
 Key Highlights of May 2020 Release
 Mule Migration Assistant Release
 What is VPC and VPN
 Important terminologies in VPN and VPC
 What is DLB and SLB
 Demo
 Networking time

4. All contents © MuleSoft Inc.
Introductions
4
• About the organizers:
– Sudeshna Mitra
– Manish Yadav
– Akshata Sawant
• About the sponsors: MuleSoft
A SHOW OF HANDS:
Who is new to this MeetUp?

5. All contents © MuleSoft Inc.
Speaker
5

6. All contents © MuleSoft Inc. 6
Meet our Ambassadors

7. All contents © MuleSoft Inc. 7
• Key Highlights of May 2020 Release
– Automate MUnit Test Cases
– Seamless coordination between Studio and Platform
– EGit Plugin
– A new Threading Model - UBER POOL
Latest Releases and Enhancements

8. All contents © MuleSoft Inc. 8
Mule Runtime 4.3.0 - Threading Model

9. All contents © MuleSoft Inc. 9
• The update Syntax
• Streaming Features and Enhancements
• Literal Types
• Period and Date Time Consistency
• Custom MIME Types
• DataWeave Modules
• Intersection Type
• Improvements to Parsing Error Messages
• New DataWeave Reader and Writer Properties
Mule Runtime 4.3.0 - DataWeave Updates

10. All contents © MuleSoft Inc.
Mule Migration Assistant
Evaluate migration complexity
Generate an initial assessment of the manual
work required for migrating individual Mule
apps
Reduce manual effort
Avoid rewriting from scratch by converting the
project structure and common connectors
(HTTP, DB, etc) into Mule 4 compatible
components
Customize with extensibility
Users can develop plugins on the open source
framework for repetitive migration tasks such
as custom connectors and complex MEL
 Jumpstart Mule 3 to Mule 4 migrations
Open
Source

11. All contents © MuleSoft Inc. 11
• What is Mule Migration Assistant (MMA)?
• How do customers assess if MMA is right for them?
• What does open source mean? How is this supported? What exact components/modules are migrated?
What is the license for this?
– More details on the MMA can be found on the GitHub self-contained documentation.
– For a complete list of the components that are included, you can inspect the module library here
• Who can contribute to the assistant?
– Customers, partners and the community are welcome in general to make pull requests and contribute to the
project.
• How much time/cost savings can MMA help with, do we have a T-shirt sizing exercise customers can do?
• What versions of Mule can we convert to/from?
• What are the dependencies for using MMA?
• How does MMA support - Dataweave, Munit, Connectors, etc.
• How will the community receive help with MMA? - Community forums
• What training are we providing for MMA specifically?
Mule Migration Assistant

12. All contents © MuleSoft Inc. 12
• What does the assistant NOT do?
These are some of the things the MMA assistant does not migrate (these are not the only ones, but the most
representatives):
- Manual migration of Cloud Connectors (for example SFDC, SAP, S3, etc).
- Manual migration of complex MEL expressions to DataWeave that cannot be automatically converted by MMA.
- Manual migration of complex DataWeave transformations that cannot be automatically converted by MMA.
- Prior migration of the DataMapper with the DataWeave Migration assistant, before running the MMA.
- Customer connectors and modules as well as any Java extensions.
• Additional documentation - migrating connectors best practices:
– https://docs.mulesoft.com/mule-sdk/1.1/dmt
– https://docs.mulesoft.com/mule-sdk/1.1/best-practices
• Additional documentation - migrating API specifications best practices:
– https://docs.mulesoft.com/design-center/design-modify-raml-specs-conform
• Sample project walkthrough - GitHub
• Video – Overview
• Video - Demo
Mule Migration Assistant

13. VPC and VPN

14. • What is Virtual Private Cloud (VPC)
• How VPC works ?
• What is Virtual Private Network (VPN)
• VPC Connectivity Methods
What is VPC and VPN

15. All contents © MuleSoft Inc.
Virtual Private Cloud
15
• A secure, private cloud hosted within a public cloud.
• VPC combines scalability and convenience of public cloud computing
with security and isolation of private cloud computing
• It allows to extend the corporate network and allows cloudhub
workers to access resources behind your corporate firewall
• Anypoint VPC uses Amazon Virtual Private Cloud for creating a VPC
• Base Anypoint VPC subscriptions comes with 2 anypoint VPC’s which
can further be associated with multiple environments. This allows to
have one for non prod environments and one for prod environments
• One can choose any region while creating VPC

16. All contents © MuleSoft Inc.
Important VPC terminologies
16
• Subnets: A subnet represents an availability zone in a VPC and is
associated with one availability zone only. A region having 3 AZ’s will have
3 subnets
• Route Tables: A route table defines a set of rules called routes which
determines where network traffic is directed in your VPC
• Load Balancers: It refers to process of distributing a set of tasks to a set
of resources for efficient processing. Anypoint platform contains 2 types of
load balancer:
• Dedicated Load Balancer
• Shared Load Balancer
• Classless Inter-Domain Routing(CIDR): It is a method for allocating
IP addresses and for IP routing. This helps in getting a range of IP
addresses allocated to our VPC

17. All contents © MuleSoft Inc.
How VPC Works
17

18. All contents © MuleSoft Inc.
How VPC Works
18

19. All contents © MuleSoft Inc.
Virtual Private Network
19
• A VPN extends a private network across a public network and enables
users to share data as their devices are connected to private network
• Encrypts private communication and provide strong degree of anonymity
• Creating a secure connection between Virtual Private Cloud and your On
Premise Data Centre or any public cloud service
• Mask the IP address to secure the online actions and makes it
untraceable
• Some of VPN types and protocol includes:
– Point to Point Tunneling
– Internet Protocol Security(IPSEC)
– Secure Shell(SSH)
– Secure Socket Layer and Transport Socket Layer(SSL and TLS)
– Open VPN

20. All contents © MuleSoft Inc.
Anypoint VPN
20
• For creating secure connection between Mulesoft VPC and On premise
Data centres or Public Cloud Networks
• Anypoint VPN supports site-to-site Internet Protocol security(IPSec)
• Mulesoft side of connection implementation is based on Virtual Private
Gateway
• Virtual Private Gateway is associated to a single VPC but supports upto 10
VPN connections
• Each VPN connections consists of 2 tunnels to connect to single IP
address at remote location
• 2 tunnels allows for increased availability for Mule VPC so both should be
connected to the endpoint
• A Mule Virtual private Gateway provides throughput of 1.25 Gbps, which
is shared among different VPN connections to the VPC

21. All contents © MuleSoft Inc.
Important Terminologies
21
● Static IP Addresses: Manually configured by device instead by a
DHCP server. The IP address does not change and is very crucial in
setting up VPN connection as it trusts only certain IP addresses
● Virtual Private Gateway(VGW): A VGW is like a VPN endpoint on
your side of connection. It can support upto 10 VPN connections and
helps in creating static or dynamic routes
● Secure Sockets Layer: SSL is protocol to secure network connectivity
for users over insecure networks
● Tunneling: Process designed to privately transmit data between
private networks. It enables network to communicate securely and
privately over a public network

22. All contents © MuleSoft Inc.
Anypoint VPC Connectivity Methods
22
● Internet Protocol Security(IPSec): To connect to On Premise Data
centre with n/w to n/w configuration. It is recommended method for
Cloudhub to On Premise connectivity

23. All contents © MuleSoft Inc.
Anypoint VPC Connectivity Methods
23
● VPC Peering: This can be used for connecting to two VPCs. It pairs
your Amazon Private VPC with Anypoint VPC. The main condition for it
to work is that they should be in same regions

24. All contents © MuleSoft Inc.
Anypoint VPC Connectivity Methods
24
● CloudHub Direct Connect: This method establishes a dedicated
network connection from your Amazon account to your Anypoint VPC.
This enables you to create a hosted virtual interface to attach to your
Anypoint VPC.

25. Load Balancers

26. All contents © MuleSoft Inc.
Load Balancer
26
● Load Balancing refers to process of distributing a set of tasks over a
set of resources with the aim of making overall process efficient
● Load Balancer is a device that acts as a reverse proxy and distributes
network or application traffic across a number of servers.
● Increases performance and reliability of the applications
● Load Balancers use some algorithms to effectively manage the incoming
traffic
○ Round Robin
○ Weighted Round Robin
○ Least Connections
○ Least Response time

27. All contents © MuleSoft Inc.
Cloudhub Load Balancers
27
• CloudHub Load Balancers are further divided in 2 parts
– Shared Load Balancer
– Dedicated Load Balancer
• Shared Load Balancer:
– Cloudhub provides a shared load balancer available to all environments
– Provides basic functionality like TCP load balancing
– Does not allow to configure custom SSL certificates and SSL rules
– Has lower rate limit to ensure platform stability of applications. Rate limit is
applied as per the application region
– Rate limit cannot be customised in case of shared load balancer

28. All contents © MuleSoft Inc.
Important Points in Cloudhub Load balancers
28
• Shared Load Balancers by default redirects the incoming requests,
where “appName” is name of the application deployed in cloudhub
and region which we are taking as “us-east-1”
– HTTP Request to “http://appName.us-e1.cloudhub.io” to “http://mule-worker-
appName.us-e1.cloudhub.io:8081”
– HTTPS Request to “https://appName.us-e1.cloudhub.io” to “http://mule-
worker-appName.us-e1.cloudhub.io:8082”
• In case of using shared load balancers the property for port is
configured is
– For HTTP: ${http.port} -> 8081
– For HTTPS ${https.port} -> 8082

29. All contents © MuleSoft Inc.
Cloudhub Load Balancers
29
• Dedicated Load Balancer(DLB):
– Handle load balancing between different workers running the application
– Define SSL configurations to provide custom certificates and enforce 2 way
SSL authentication
– Configure proxy rules to map application to custom domains
– Has lower rate limit to ensure platform stability of applications. Rate limit is
applied as per the application region
– Rate limit cannot be customised in case of shared load balancer
– To use DLB, one need to create a Virtual Private Cloud
– We can assign upto 4 load balancers to a DLB

30. All contents © MuleSoft Inc.
Important Points in CLoudhub Load balancers
30
• Dedicated Load Balancers provides alternative domain name to route
applications running on port 8091 for HTTP and 8092 for HTTPS
• We can configure the load balancer requests to map to different
application domain name
• In case of using dedicated load balancers the property for port is
configured is
– For HTTP: ${http.private.port} -> 8091
– For HTTPS ${https.private.port} -> 8092
• DLB exposes a domain name which resolves to 2 IP addresses
accessible from outside cloudhub VPC network. While creating a DLB
with name “dlbName” the domain name is as :
– “dlbName.lb.anypoint.dns.net”
• One can access the application using below URL:
– “http://appName.dlName.lb.anypointdns.net” and
“https://appName.dlName.lb.anypointdns.net”

31. All contents © MuleSoft Inc.
Dedicated Load Balancer Architecture
31

32. All contents © MuleSoft Inc.
Take a stand !
32
• Nominate yourself for
the next meetup speaker
and suggest a topic as
well.

33. All contents © MuleSoft Inc.
What’s next
33
• Share:
– Tweet your pictures with the hashtag #MuleMeetup #MuleSoftMeetup
– Invite your network to join: https://meetups.mulesoft.com/mumbai/
• Feedback:
– Contact your organizers Manish Yadav, Sudeshna Mitra and Akshata Sawant to suggest topics
– Tweet your organizers at @SudeshnaMitra14, @Manish_Kyadav, @sawantakshata02
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
– Follow us on Instagram (mumbai_mulesoftofficialpage)
– Your Feedback is Food for us
• Our next meetup:
– Date: TBD
– Location: Mumbai
– Topic: TBD

34. Networking time
Introduce yourself to your neighbors!

35. See you next time
Please send topic suggestions to the organizer

36. THANK YOU