Mule soft indore meetup 2

MuleSoft® Meetup #2 (Virtual)
Indore
19 Sep 2020

All contents © MuleSoft Inc.
Agenda
2
• Introductions and Welcome
• Session 1: Deploying Mule Applications
• Quiz Time
• Session 2: Object Store in Depth
• Q&A and MuleSoft Community Experience Sharing

Introductions
3
Organizer: Pradhan Yash Sharma
https://meetups.mulesoft.com/indore/
A SHOW OF HANDS:
Who is new to this Meetup?
Sponsor: YASH Technologies Pvt. Ltd.
mulesoftindore@gmail.com

Pradhan Yash Sharma
• Certified MuleSoft Developer
• Active open-source contributor
• Leading MuleSoft Meetup Indore Chapter
• Working in YASH Technologies as Senior Developer
• Java Enthusiast member of Java Community Process at
Open-JDK
Speakers
pradhanyashsharma20@gmail.com
@PradhanYashSha1
https://www.linkedin.com/in/pradha
nyashsharma/

All contents © MuleSoft Inc. 5
Kirti Gurjar
• MuleSoft Certified Integration Architect
• MuleSoft Meetup Speaker
• Working in YASH Technologies as Lead Consultant
gurjarkirti3@gmail.com
https://www.linkedin.com/in/kirti-
gurjar-b322b479/
Speakers

• Please keep yourself on mute unless you have any question.
• You can also write down your questions in chat section.
• We encourage keeping your video on for making our meetup interactive.
• Once you join, write down your registered name in chat section so we will have an
attendance.
• As this is our first virtual Meetup, we appreciate your valuable feedback.
Guidelines for Virtual Meetup

Deploying Mule Applications
Session 1
Pradhan Yash Sharma

Main Components of Anypoint Platform

Run and Execute the Hello Mule Project

Mule Runtime Engine
10

Mule runtime engine (Mule) is a lightweight integration engine
that runs Mule apps.
It is a single, universal engine for connecting applications, data,
and devices.
Users can build Mule apps to connect systems, services, APIs,
and devices using MuleSoft’s API-led connectivity instead of
point-to-point integrations.
Mule Runtime Engine

Features of Mule Runtime Engine
Combines data &
application
integration
Single runtime
deployable in cloud
or on-premises
Enables SOA, ESB
patterns, SaaS, API,
Microservices
Extensible to SOAP,
REST, JMS, AMQP,
AS400, IoT
Real Time and Batch
Processing
Map and Transform
data with Dataweave
Open Architecture
Support
Common Standards
and New
Technologies

• Mule applications are configured to run in Mule runtime engine.
Deployment Targets
MuleSoft
App
CloudHub
Anypoint
Runtime
Fabric
On-Premise
Mule
instances

Anypoint
Studio
Anypoint Runtime
Manager
Anypoint Platform CLI
Mule Maven plugin
Deployment Tools

CloudHub or Anypoint Runtime Fabric, these services take
care of the Mule runtime engine instances needed to run
applications.
On-premises, the installation of Mule runtime engine is
required.
Deploy Applications

Deployment Models
Anypoint Platform Private
Cloud Edition

Deployment Strategies
17
Anypoint Platform
Private Cloud Edition
Runtime Manager – Cloud
Console
App Deployment Target -
Cloudhub
Runtime Manager – Cloud
Console
App Deployment Target –
Your Own Servers
Runtime Manager – Private
Cloud Edition
Your Own Servers
Runtime Manager – Private
Cloud Edition
PCF Repository
Runtime Manager

Deploy anywhere from Single Interface
Runtime Manager
18
Runtime
Manager
CloudHub
Runtime
Fabric
On Prem

Runtime Manager: Architecture
19

• Cloud version supports deployments on Cloudhub or elsewhere
• On-Prem version supports deployments except Cloudhub
• On-Premise can send the data to third parties
• Insights, Analytics and Monitoring fully supported with cloud version
Runtime Manager: Architecture

Runtime Manager: Key Capabilities
21

Cloud Console Cloudhub Deployment
22
Cloudhub
Infrastructure Platform As A Service
Automatic Availability of all
components
Auto Load balancer if multiple
workers are used
All Components are at one place –
Hassle Free Integration

Cloud Console to On-Prem Deployment (Hybrid)
23
Greater Flexibility and Tighter
Security
No Application Data flows to
Anypoint. Only matrices are used.
Concept of Servers, Server Groups
and Clusters
High Availability Scenarios with your
own Servers

On-Prem Console Own-Prem Deployment
24
Suitable for Customers with Strict
Regulatory or Compliances
Requirements
Containerized Distribution
Customer’s private Cloud/DC
AnyPoint Platform Private Cloud
Edition

Comparison: Deployment Strategies
High Availability Automatic Custom By Client
Logging Automatic By Client By Client
Alerts Automatic Custom NA
Server, Server
Groups, Clusters
Automatic Custom NA
Security Automatic By Client By Client
Dashboard & Insights Automatic By Client NA

Comparison: Deployment Strategies
Object Store
Infrastructure
Automatic
By Client
By Client
Monitoring Automatic Custom By Client
Troubleshooting Automatic Custom By Client
Scheduling Automatic Custom By Client
Load Balancing Automatic By Client By Client
Shared Resource
Support
Automatic By Client By Client

Servers
27
Standalone Servers
Runtime Manager gets the data
about Server and manage
applications
Must create the server to manage it
through Runtime
Remote Servers can be managed
individually

Server Groups and Clusters
28
A Group of Servers can be managed parallelly through a Server Group or Cluster
Server Groups Clusters
 The instances of applications are completely
isolated from each other.
 Provides Redundancy
 In case of disaster, applications can be
restored seamlessly and quickly with less
downtime.
 Eliminate duplication of Effort because there
is no need to restore each application
seperately.
 Both the nodes are aware of one another
and share common information and
synchronize statuses
 An on-prem cluster enables up to eight
servers to participate in HA unit.

Deploy an
Application from
Runtime Manager
Deploy an
Application
from Studio
Deploy an
Application
from the
Command
Line
Deploy to CloudHub

Deploy an Application from Runtime Manager
Application Name
Upload JAR File
Deploy Application

• Open your application in Studio.
• In Package Explorer, right-click the project folder and select Anypoint Platform >
Deploy to CloudHub.
• If this is your first time deploying from Studio, provide your Anypoint Platform
credentials at the prompt.
• Studio stores your credentials for future use. You can manage these credentials by
selecting Anypoint Studio > Preferences > Anypoint Studio >
Authentication.
• After you sign in, you see the Deploying Application page.
• Click Deploy Application.
Deploy an Application from Studio

• Download and install NodeJS, Git and npm.
– npm install -g anypoint-cli@latest
– anypoint-cli --username="PradhanYashSharmaMule“ <<user_name>>
– use environment Sandbox <<env_name>>
– runtime-mgr cloudhub-application deploy mulesoftindoremeetupdeployent-cli
<<app_name>> C:Usersyash.sharmaDesktopmulesoftindoremeetupdeployent.jar
<<location>>
– runtime-mgr cloudhub-application list
Deploy an Application from the Command Line

• Downloading Mule
– $MULE_HOME/bin/mule
• Add Servers to Runtime Manager
– From Anypoint Platform, select Runtime Manager.
– Click Servers in the left menu.
– Click the Add Server button.
– Copy command to copy the amc_setup
• $MULE_HOME/bin/mule install
• $MULE_HOME/bin/mule start
• Deploying Using the Runtime Manager REST API
Deploy to On-Prem

• Deploying Using the Runtime Manager REST API
– Configure the CloudHub deployment strategy in your project pom.xml
<armDeployment>
<muleVersion>${app.runtime}</muleVersion>
<uri>https://anypoint.mulesoft.com</uri>
<target>${target}</target>
<targetType>${target.type}</targetType>
<username>${username}</username>
<password>${password}</password>
<environment>${environment}</environment>
</armDeployment>
• Package the app and execute the deploy goal
– mvn clean package deploy –DmuleDeploy
Deploy to On-Prem

• Mule runtime engine: https://docs.mulesoft.com/mule-runtime/4.3
• Private Cloud Edition: https://docs.mulesoft.com/private-cloud/2.1
• Deploying to CloudHub: https://docs.mulesoft.com/studio/7.6/deploy-mule-
application-task
• Anypoint Platform CLI: https://docs.mulesoft.com/runtime-manager/anypoint-
platform-cli-commands
• Download Anypoint Studio 7: https://www.mulesoft.com/lp/dl/studio
• Download Mule 4 standalone: https://www.mulesoft.com/lp/dl/mule-esb-enterprise
References

Object Store in Depth
Session 2
Kirti Gurjar

Agenda
43
• Introduction Of Object Store
• Object Store Variants
• Features
• Limitations
• Walkthrough and Demo

Object Store
Object Store is a fully managed services that enables sharing of states in multi-clustered
environments on CloudHub without any risk of state loss during disaster events or
application restarts.

Use cases
• Storing synchronization information, such as watermarks.
• Storing temporal information such as access tokens.
• Storing user information.
• For state management:
– Between the flow Execution
– Between iterations when processing a collection of elements like batch
processing or, to aggregate results such as a total price or total count.

Continued…

• Object Store as Connector
• Object Store in form of REST API
• Reference Link to download Object Store -
https://www.mulesoft.com/exchange/org.mule.connectors/mule-objectstore-
connector/
Ways to access the Object Store service

• Used by Customer-Hosted and RTF Run-time Planes
• Available in form of OS connector
• Available only in us-east region
• Local to worker and always Transient
• Persists keys for 30 days unless updated
• 1 MB Value Limit
• Limited to 100k Keys/App
Object Store V1

Object Store V2
51
• Simple key value store
• Available in form of OS connector and Rest API
• Synchronized access at key level
• Uses TLS for transport and FIPS 140-2 compliant encryption standard for data
at rest
• Supports unlimited keys/app
• 10 MB max value size
• Is preserved upon application redeployment and restarts
• Is deleted upon application deletion

Object Store Types

Continued…
• Non-persistent in memory storage is the fastest way to access data, but is the
least reliable/durable
• Local persistent storage, such as to a file system, is slower but more reliable,
and not shared
• Replicated in-memory data grid storage lies somewhere between in-memory
and on-disk
• An external storage system may be the most reliable and can be shared, but
also may be much slower

Continued…

Object Store V2 Features

Limitation
• Not a universal data storage solution
• Does not support transactions
• Does not replace an actual DB and not suitable for searches, queries, etc.
• Data is automatically removed after a set amount of time – 30 days for
OSv2
• Limited to 10 TPS per app for “free tier” – Can licence higher TPS

Operations
• Clear — Removes all the contents in the store.
• Contains — Checks if there is any value associated to the given key. If no value exists for
the key, then false is returned.
• Remove — Removes the value associated to the given key. If no value exists for the key,
then an OS:KEY_NOT_FOUND error is thrown.
• Retrieve — Retrieves the value stored for the given key. If no value exists for the key,
behavior depends on the defaultValue parameter.
• Retrieve all keys — Returns a List containing all keys that the object store currently holds
values for.
• Retrieve all — Retrieves all the key value pairs in the object store.
• Store — Stores the given value using the given key. This operation can be used either for
storing new values or updating existing ones, depending on the value of the failIfPresent.

Object Store Instances
• Default Object Store
• Global Object Store
• Private Object Store

MuleSoft Community Experience Sharing
Ask Questions / Share Feedback!

What’s next
63
• Share:
– Post your pictures with the hashtag #MuleIndoreMeetup on LinkedIn/Twitter
– Invite your network to join: https://meetups.mulesoft.com/indore/
• Feedback:
– Contact your organizer Pradhan Yash Sharma to suggest topics at
mulesoftindore@gmail.com
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program

See you next time
Please send topic suggestions to the organizer

Mule soft indore meetup 2

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Mule soft indore meetup 2

Similaire à Mule soft indore meetup 2 (20)

Dernier

Dernier (20)

Mule soft indore meetup 2