Meetup hyderabad mule-4.x

23th FEB,2019: More in Mule 4 And Anypoint Studio
Hyderabad MuleSoft Meetup

All contents © MuleSoft Inc.
Agenda
2
• 11:00 AM Introduction
• 11:15 AM Presentation: Mule 4 /
Anypoint Studio 7-Deep Drive
• 12:30 AM Tea, Coffee and Snacks break
• 01:00 PM Q & A
• 01:45 PM Networking and Plan for Next
Meetup

Agenda
3
• Introductions
• What’s new with Mule 4
• New Message Structure
• Transformation and data Simplified
• DataWeave 2.0
• Seamless Data Access
• Error Handling With Mule 4
• Class Loader Isolation
• Mule 3 Complexity Flow Vs Mule 4 Productivity Flow

Introduction : Organizer, Speaker and You
4
Santosh Ojha Manish Yadav Sravan Lingam
A SHOW OF HANDS:
Who is new to this Meetup?

What’s New With Mule 4?
6
• Improving speed of delivery and accelerating developer on-ramp
through a simplified language, error handling, and event and
message model.
• Generating connectors automatically from RAML specs with REST
connect.
• Simplifying upgrades with class loader isolation.
• Mule 4 ships with a new reactive, non-blocking execution engine.
• Users no longer need to convert data into a set of objects to access
it.
• Error Handling - Easier and more powerful error handling with a new
Try scope.

What’s New With Mule 4
7
• Expression language - The Mule Expression Language has been
replaced with the DataWeave language so that you work with data
and learn Mule more easily.
• DataWeave - DataWeave includes minor changes to simplify the
syntax and make it easier to learn.
• Studio 7 - Features a simplified palette, improved Maven integration,
and many other usability improvements.
• Runtime engine - The internal execution engine has been updated
with a new self-tuning and non-blocking reactive engine. This allows
for better performance and scalability out-of-the-box.

What’s New with Mule 4
8

Triggers, Connectors, and APIs in Mule 4
9

Simpler Flows - Validators
Mule 3 Flow
Mule 4
Choice Replacement Choice Replacement

Language Agnostic - Java Optional
11
Business Formats:
● JSON
● XML
● Java
● CSV
● and more!

Mule 4 Event Model
New Message Structure

Mule 4 Event Model
13
• Event Flow

Event and Message
14
• Events have a Message and
variables
• Each message contains
– Payload – e.g. HTTP body, FTP file,
etc
– Attributes – HTTP headers/uri
params, File information, etc.
• Variables can any object: data,
attributes, or even another
Message!
Message
Event
Payload
Attributes
Variable1 (Object)
Variable2 (Message)

What goes on Attributes
15

Transformation and Data Simplified
16
• Formal type system defined. Types can be
– Binary
– CSV
– JSON
– XML
– Object (and sub types – List, Attributes, etc)
– Scalar – Number, String, etc.
• Binary representation is transparent. Don’t worry about
InputStream/byte[]/etc
• If you feel the need to do Object to Byte Array/String/etc –
you’re doing it wrong or it’s a bug.

DataWeave 2.0
18
• Mule 4 introduces DataWeave as the default expression
language,replacing Mule Expression Language (MEL) with a scripting
and transformation engine.
• Java interoperability: Static methods can be executed through
DataWeave.
• Simplified syntax: All operators are now functions, making
DataWeave easier to learn.
• New advanced capabilities: Call Java functions directly,use multi-line
comments, and define function types and variable types with type
inference

DataWeave 2.0
19
• Default expression language of Mule 4.
• More supported data formats such as “application/x-www-
formurlencoded”, and “multipart/*”.
• Data extraction without explicit data conversion.
• More functions and operations for data manipulations

Simplified DataWeave
20
• Operator precedence in Mule 3 took some remembering. Now, all operators
are functions
– Mule 3: upper pluralize dasherize "maxMule"
– Mule 4: upper(pluralize(dasherize("maxMule")))
– More parentheses, but with auto-completion should be easier for new users
• Traits are now functions too
– Mule 3: payload is :empty
– Mule 4: isEmpty(payload)
• Pascal style type names
– Mule 3: payload.foo as :string
– Mule 4: payload.foo as String

DataWeave Enhancements
21
• Variables/function params typing
• Multiline comments
• Imports
%dw 2.0
import dw::core::Strings
output application/json
---{
'plural':Strings::pluralize("meetup"
) }
/**
*@Author-Manish Yadav
*/
fun foo(x: String):String = x
var myVar: String "Weave"
Declare static Java functions:
And access them directly in DataWeave:
public class MyUtilClass{
public static String reformat(String
input) {
return ...;}
}
%dw 2.0
import
java!forslidesmuckaround::MyUtilClass
---
{
date:
MyClass::reformat(myInputString)
}

Seamless Data Access
22
What do you think Here.
• Java Knowledge required ?
• Always Conversion required?
• Access of Payload with transformation?
payload.email
match /([a-z]*)@([a-
z]*).com/
payload map {
name: $.name,
dob: $.dateOfBirth as
:date, title:
lookup($.titleCode),
…
}

Iterating a JSON Array
23
You don’t think ?.
• You need to aware of Payload
type?
• You need to aware of the type
of payload For Each accepts?

Iterating a JSON Array
24
Thinking???
How smart Mule Runtime 4 is?
It Knows everything???
1.DataWeave knows how to
iterate a JSON array
2.You don’t even need to specify
it’s JSON
3.You don’t need to worry about
for each inner working.

With Mule 4
No More Message Enricher

Enrichment: Think Different??
26
• Directly output data into variables
• The payload goes to the variable, but you can send the message or
attributes too
• For other use cases, use transform to enrich

Simplified error handling and try scope
28
1. New try block - catch errors anywhere in flows
2. See errors at design time
3. Simplified syntax when using transactions and
error handling
4. Re-propagate errors
5. Java Exceptions aren’t needed (but you can still
use them!)

Simplified error handling and try scope
29
Every component has a list of its possible error
Errors are easy to discover in Studio

Error Types: Part of every component
30
Description
Duplicate entry '5' for key 'PRIMARY'.
Type
DB:QUERY_EXECUTION

Error Handler
31
• Event Step in case of exception occurs at 2.

Error Handler
32
• Event Step in case of exception occurs at 3.

Mule Error Description
33
• For example HTTP request failed with Wrong credential.
Major Improvement:
• Only two strategy of On Error Scope, You can handle all possible
error in Mule 4.
• In Mule 3,Error can be handled at Flow/Sub Flow or Private Flow but
now we can handle the error at event level of message.

Mule 4 Runtime
Self Tuning Engine

Self-Tuning Runtime Engine
35
Non-blocking execution engine.
Can configure sizing of the pools and Custom thread
pools creation for some task
This engine makes it possible to achieve optimal
performance without having to do manual tuning steps,
such as declaring exchange patterns, processing strategies
or threading configuration.

Self-tuning runtime engine
36

With Mule 4
Class Loader Isolation

Class Loader Isolation
38
• With new class loader isolation between Mule
applications, the runtime, and Anypoint Connectors,
any library changes that occur internally do not affect
the application itself.
• Connectors are distributed outside the runtime as well,
making it possible to get connector enhancements and
fixes without having to upgrade the runtime or vice
versa.

Mule 3 today: a medium complexity flow
39
ObjectStore
Transports
JavaWatermark
Streams
Connectors
Enricher
DataWeave
22 Concepts 13 Steps
Java and .NET
specialists
MEL

Integration, Simplified - 3 to 4x productivity
40
Java & SFDC
specialists
13 Steps22 Concepts9 Concepts 5 Steps
Specialists &
generalists

Take a stand !
41
• Nominate yourself for
the next meetup speaker
and suggest a topic as
well.

See you next time
Please send topic suggestions to the organizer

Meetup hyderabad mule-4.x

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Meetup hyderabad mule-4.x

Similar to Meetup hyderabad mule-4.x (20)

More from Santosh Ojha

More from Santosh Ojha (14)

Recently uploaded

Recently uploaded (20)

Meetup hyderabad mule-4.x