Thailand MuleSoft Meetup Recap

June 22nd 2020
Thailand MuleSoft Meetup

All contents © MuleSoft Inc.
Our Partners
2

Agenda
4
• 3:00 pm: Welcome & Introduction
• 3:15 pm: What's new in MUnit? Easier unit testing easier in Mule
• 3:40 pm: Building a business case for integration
• 4:10 pm: Quiz & prizes
• 4:30 pm: Meetup concludes

Speaker
6
Greg McCreanor - Senior Manager,
Solutions Engineering ASEAN
MuleSoft
Greg has been recently promoted to SE Manager and was a Principal Solutions Consultant for
MuleSoft based in Singapore and has over 20 years of experience working in both core systems and
integration technologies. Since joining MuleSoft he has brought valuable insight to our customers and
prospects about their current technical challenges and how to move to the next generation of
solutions. In the last 3 years, he has worked extensively with our public and private sector customers
within Australia, New Zealand, and South East Asia

Speaker
7
Manop Prapancharoensin
VP - Platform & Technology
Nexus System Resources Co., Ltd.
Manop graduated with a master degree in computer engineering and business administration. He started his SAP
career as an ABAP programmer position in 1998 and has since then been active in various roles such as ABAP
consulting lead, Business Intelligence consulting lead and project manager in both local and foreign MNCs. With
much a vast experience in development projects, he is also well versed in business process management,
business workflow, IT system management, application integration and also has had the opportunity to be a
lecturer for many private companies. Currently, he’s responsible for managing all technical teams that includes
S/4HANA, BW/4HANA, SAP PO, BOBJ, SAP Analytics Cloud, MuleSoft, BY, .NET and JAVA development.

What’s new in Munit?
Easier unit testing easier in Mule
Manop Prapancharoensin
Nexus

Overview of MUnit
What will we be talking about?
MUnit test recorder
in the new Mule 4.3
/ Studio 7.5 Release
Where to go
next?

Overview of MUnit
What will we be talking about?
MUnit Test Recorder
in the new Mule 4.3
/ Studio 7.5 Release
Where to go
next?

What is MUnit?
● MUnit is the testing
framework specifically
targeted to testing Mule
applications
● It natively supports unit
and integration testing
on APIs and Mule apps
in local and CI/CD
environments (via
Maven).

How do you use MUnit?
1 Use MUnit to build test
flows (technically called
test suites in the
industry) focused on
executing Mule flows.
Each test is essentially a
Mule flow.
2 Use components from
MUnit and generic Mule
components to build test
flows
3 Test flows execute in
a Mule runtime and
report results
1 2
3

Setup
5 4
Implement
4
Design Deploy
2 2 1 8 hours with MuleSoft
26 hours
4
1.5
Unit test Manage
& Monitor
Comparison done by a leading financial services firm in partnership with a major system integrator
0
.
5
1
4 5
38%
26 hours
Decreases
development
time by:
for a medium
complexity
for a high
complexity
for a low
complexity 47% 67%
Head-to-head comparison vs. legacy middleware

Unit tests are hard
to write
Unit tests are hard
to read
Unit tests are hard
to understand
The pain of testing today: it is not fast
“
”
“
”
“
”

Unit tests are hard
to write
Unit tests are hard
to read
Unit tests are hard
to understand
The pain of testing today: it is not fast
“
”
“
”
“
”
✅

MUnit test recorder
Accelerate time to delivery by automating the creation of
unit tests based on the execution of the application at
design

Test recorder - GA on April 30th!
● Automatically generate (“write”) MUnit tests
based on the execution of application at
design
● Takes the setting of the input and output
events for unit and integration tests to build
MUnit tests
Get started writing MUnit tests
Documentation
● MUnit developer tutorial on how to create
your first MUnit tests in Anypoint Studio
● Targeted documentation (“cookbook”) of
MUnit specific examples and best
practices

Anypoint Studio 7.5 and Mule 4.3
19
Generally available April 30th
Automate test creation
Capture flow execution with the new MUnit
test recorder to automatically generate
tests
Scale with confidence
Leverage runtime performance
improvements for more efficient code
execution
Collaborate on API Specs
Pull and update API specifications within
Studio and merge them back to Design
Center

Download Studio
7.5 / Mule 4.3 -
April 30th
Where to next?
Developer Meetup
at CONNECT - June
25th
developer.mulesoft.com

Building the Business Case for Integration
Greg McCreanor - MuleSoft

The Language of Money
What is it & How do you find
it?
Business Metrics & KPIs
Business Strategy
Industry challenges & insights
Why is it important?
Existing perceptions of
integration

The value of integration
What is it & How do you find it?
Depends on the use case
It’s not what, but how and why….
Typical examples:
- Reduced mean time to repair
- Speed to market
- Security
- Infrastructure optimisation
Total = $7,783,171
Three-year, risk-adjusted total present value
Customers can realize 445% ROI with Anypoint Platform
Forrester TEI Study shows MuleSoft delivers $7.8 million in benefits for an organization
Source: Forrester TEI Study on Anypoint Platform
Increase in API reuse value through Anypoint Platform
Time savings toward building new APIs
Cost savings from reduced maintenance of APIs and integrations
Incremental revenue from contributions to projects
Cost savings for retired technologies

Comparing costs
Typical considerations
Approach to licensing
Initial license cost
Implementation costs
Training costs Often missed
Additional licenses as more
capacity required
Developer productivity
Increased maintenance
overhead
Architecture lock in
Speed to market
Security

Self Serve Collaborative Value
Assessment

Business Outcomes delivered
Business
Objectives
Initiatives
Technology
Use Cases
Value
Increase operational
efficiencies/agility (IT)
Increase operational
efficiencies/agility (non-IT)
Legacy modernization
Portfolio rationalization
Move to the Cloud / Hybrid
Maintenance spend reduction
Business process automation
Field and Support (agent) productivity
Use APIs to standardize the way systems
connect to each other. Plug/unplug
systems using a hybrid integration
platform.
Adopt a "plug and play" approach to
integration, wrapping systems in APIs and
creating "building blocks." Use "building
blocks" to build new, more efficient
processes.
-Lower IT operating costs
-Improved business agility
-Lower operating costs
-Maintain and improve competitive advantage
-Improved business agility
-Improved employee productivity & satisfaction
Improve the customer experience
(increase customer acquisition,
spend, retention)
360-degree customer view
Mobile/eCommerce
Omnichannel
Adopt a "plug and play" approach to
integration, wrapping systems in APIs and
creating "building blocks." Use "building
blocks" to build new, customer-engaging
process and applications.
-Improved customer experience
-Improved reputation and brand
-Maintain and improve digital competitiveness
-More revenue, better customer retention,
higher spend per customer
Sample output

Challenges in the process of being overcome with MuleSoft
API strategy →
- Lack of clearly documented and socialized API
strategy
- Lack of clear mandate to standardize
connectivity of systems, processes, and data
→
- Lack of alignment between business and IT
- Integrations driving limited business value
- High IT operating costs
Developer on-ramp →
- Developers required to learn multiple coding
languages to integrate applications
→
- Long developer on-ramp period
- High IT onboarding costs
- Long time to full productivity
Area Observation Implication
Integration technology
& tooling →
- No integration platform. Systems connected in a
point to point, non-standard way
→
- Slower project speeds
- Delayed time to market
- Poor project quality
- Suboptimal security
- High maintenance costs
- Poor governance
Sample output

Challenges in the process of being overcome with MuleSoft
Re-use →
- Limited to no reuse of integration code across
projects
- Limited use of or no repository to store reusable
pieces integration code
- Lack of an IT operating model that encourages
reuse or collaboration across development teams
→
-Slow project speeds
- Long time to market
- Poor project quality
Integration security →
- Security policies have to be manually coded into
integrations
- No consistent or governable way to check that all
endpoints are sufficiently secured
- Maintaining security of integrations is manual
→
- Poor security
- High IT operating costs
Area Observation Implication
Integration
development →
- Systems and applications are integrated
manually
- Duplicative development efforts - the same
integration code is written for each project
→
-Slow project speeds
- Long time to market
Sample output

Value realized (1 of 6)
We estimate that you have achieved $4,589,583 in value since adopting MuleSoft.
Sample output

Value realized (2 of 6) Sample output

MuleSoft CONNECT – Sydney 2019
- Presentations from Sydney CONNECT breakouts:
https://library.mulesoft.com/connect-2019-Sydney
- Sydney had the largest CONNECT meetup globally
- 54 people certified at/off the back of Sydney CONNECT
- Save the date (…and Budget!):
- Sydney Digital CONNECT 2020 will be on 25 June

Get your browsers out!!
• It’s Kahoot Time

See you next time
Please send topic suggestions to the organizer

Thailand MuleSoft Meetup Recap

Thailand MuleSoft Meetup Recap

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Thailand MuleSoft Meetup Recap

Similar to Thailand MuleSoft Meetup Recap (20)

Recently uploaded

Recently uploaded (20)

Thailand MuleSoft Meetup Recap