Manila MuleSoft Meetup #4 January 2019

January 31, 2019 : Journey to Success with Mule
Manila MuleSoft Meetup #4

All contents © MuleSoft Inc.
Our Partners
2

Selfie Time
3
Share Your Pictures
• Tweet your pictures with the hashtag
#ManilaMuleSoftMeetup
#MuleSoftMeetup

Agenda
5
• 6:30 pm: Registration, arrivals, food and drink
• 7:15 pm: Introduction
• 7:25 pm: Journey to Success with Mule
• 7:45 pm: API Design
• 8:25 pm: Networking time, games, food and drink
• 8:55 pm: Wrap up

Organizers
7

Speaker
8
Manila MuleSoft Meetup Organizer and
WhiteSky Labs Senior Integration Consultant.
He has been part of the IT industry for 10 years
with 6 years of extensive experience in JAVA.
He has worked with companies such as HP,
Daimler and BDO. His mission is to build
MuleSoft community here in the Philippines by
sharing his experience and knowledge with
fellow like-minded Mule enthusiasts.

Speaker
9
Greg has been working in the IT industry for 4
years. He is currently working as an Integration
Consultant at WhiteSky Labs, providing digital
transformation for top companies around the
world. His expertise mainly focused in banking
solutions and full stack development.

Introductions
1
0
Who are new in MuleSoft Meetup?
Introduce Yourself
• Name
• Background
• Experience in Mule

By Christopher Co
Journey to Success with
Mule

Topics
• Challenges in Integration Space
• Microservices and APIs
• MuleSoft Products and Licensing

Introduction
13

In an Alternate Universe Far Far Away…
Characters used in this presentation are copyright of DreamWorks Animation

All contents © MuleSoft Inc. 16
HOPPY

All contents © MuleSoft Inc. 17Characters used in this presentation are copyright of DreamWorks Animation

Customers Are Evolving
18
I will just have to
wait 2 weeks for
my dress
I want my
beautiful dress
NOW!

Higher Customer Expectation
19
Customers Demand
- More Speed
- More Service

Market New Entrants
20
Startups
- Hyper Agile
- Hyper Fluid
- Can Pivot on a Dime

Harder to Get Partners
21
New Partnership Opportunities are being lost
because of a Lack of Easy API Integration

Increasing Demand: New Products and Services
22

Point to Point Architecture
23

Point to Point Architecture
24
● Difficult to Maintain
● No Reuse
● Costly
● Not Scalable
● Restriction of
Technology Stack

735 Stores Closed
TROLL

Meet Max the Mule
27Characters used in this presentation are copyright of DreamWorks Animation

Indirect Competitors
29

New Partnerships
30

MicroServices
31
• https://www.youtube.com/watch?v=SouNISAnXlo

API
32
Think of API as a
contract of actions for
requesting a service.

API-Led Connectivity
33

API-Led Connectivity
34

Application Network
35

Application Network Platform
36
• 1600+ enterprises use Anypoint Platform to build an application
network to accelerate development by 3x.

Design your APIs
37
Anypoint Design Center
● Build Integration Flows
● Design APIs with RAML
● Reuse API Fragments

Share your APIs
38
Anypoint Exchange
• Save
• Share
• Discover
• Reuse

Manage your APIs
39
Anypoint Management Center
• Manage Users
• Performance Monitoring
• Analyze Traffic
• Monitor SLAs

Secure your APIs
40
• Secure Your Data
• Control Access
• Defend Critical APIs
• Basic Auth
• OAuth 2.0
• XML Threat
Protection
• Many more...

Mule Runtime Engine
41

What does Anypoint Design Center do?
42
• A. Design APIs with RAML
• B. Reuse API Fragments
• C. Build Integration Flows
• D. All of the Above

Question
What is the architectural design that structures an application into a
collection of loosely coupled services which allows organizations to
achieve agility and realize lower cost?
A. Mule
B. APIs
C. Point to Point architecture
D. Microservices

Anypoint Platform Plans
44

Platinum Plan

Titanium Plan

Got Questions on Anypoint Platform Plan?
https://www.mulesoft.com/anypoint-pricing

Customers
48

ASICS Speeds Up IT Project Delivery by 2.5x
49
“One of the most difficult parts of development is creating connections.
We can waste hours and hours on these tasks. Instead, Anypoint
Platform connects all these different systems, making developers' lives
easier.”
Phil Connaughton, Director of Engineering, ASICS Digital

“At JetBlue, we’re focused on humanizing the travel experience and
rethinking our approach to customer service, including deploying
mobile payments and being the first airline to roll out onboard
purchases using Apple Pay. The tokenization capabilities within
MuleSoft’s Anypoint Platform allow us to secure credit card
transactions flowing through JetBlue eCommerce Platform, so that we
can drive innovation and agility without compromising security.”
Vitaly Faida
Manager of IT Product Release Engineering, JetBlue

Yeah yeah yeah… All of that sounds great. But…
52

Topics
• Anypoint Platform
– API fragment & libraries
– RAML specification, versioning and raml dependencies as maven
dependencies
– https://raml.org/

API Designer
• Introduction
• Demo
• Q&A

API Design
• Who’s gonna be using the API?
• Who are the end users?
• What’s the purpose of the API?
• What type of API are we building? Why?
• How are we going to maintain the API?
• How are we going to document the API?

API Design – Done?

API Design
• How are we going to let developers interact with the API?
• How are we going to manage authentication, provisioning,
throttling, and security?
• How are we going to manage support? Or are we going to even
manage support?

API Design – Build a prototype

API Design – Problems

Introduction of RAML Specification
• RESTful API Modeling Language
• RAML enables developers define their API with tools to design, prototype,
document and allow user interaction.
• RAML was designed to encompass the entire API Lifecycle RAML was designed to
encourage careful design and code reusability (Resource Types, Traits, Data
Types, Examples)
• Based on YAML, RAML is designed to be human readable (meaning even non-
programmers can read and edit it)

Spec Driven Development
• Define your API before coding
• Reuse Codes
• Mock and get User Feedback
• Make Necessary Changes
• Start Coding

Advantage of RAML
• RAML will let you see what your API looks like as you design it,
using easy to read plain text.
• Let’s you define your API with only a few lines of code.
• You can easily make changes on your API whether it’s the design or
documentation.
• You can let your customers, partners, or even your own internal
engineers interact with the mocked out API to either review and
build off of.

Demo - Creating RAML Specification

API Design

Question 1
RESTful API Modeling Language is a human readable language derived
based on what data serialization language?
a.) Java
b.) YAML
c.) Spanish
d.) Klingon

API Fragments
• An API fragment is a RAML document that has a version and an identifier, but is not in itself a
complete RAML specification
• It can be in the form of the following:
– Trait
– Resource Type
– Type
– Example
– User Documentation
– Library
– Annotation Type
– Security Scheme

API Fragments
• It’s a key part of API development because it can help you isolate
design flaws or problems before you write a line of code.
• Instead of starting every project from scratch, you can reuse
fragments and APIs to accelerate project delivery.

Question 2
What do you call a RAML document that has a version and an
identifier, but is not a complete RAML specification?
a.) Traits
b.) Fragments
c.) Shrapnel
d.) Debris

API Versioning
• Versioning is a process of naming and distinguishing between a
series of draft documents which lead to a final (or approved)
version, which in turn may be subject to further amendments.
• Most of the APIs need to release new versions to provide new
capabilities and intent.
• is important for documents that undergo a lot of revision and
redrafting and is particularly important for electronic documents
because they can easily be changed by a number of different users.

Benefits of API Versioning
• Traceability
– Being able to see clearly how the project has evolved in the past, and how it
is currently evolving, gives project managers the tools they need to steer it in
the right direction.
• Assurance
– Develop Fearlessly
• Backup
– Not all updates are good updates

Question 3
What is the process of creating and managing multiple releases of an
API?
a.) Caring
b.) Loving
c.) Versioning
d.) Managing

References
• Lego Picture
– https://medium.com/@thiagonascimento/building-business-like-
lego-blocks-api-economy-4cae843cba33
• Document Picture
– https://www.iol.co.za/mercury/network/easy-ways-to-scan-and-
share-documents-in-seconds-15829883
• Time is money Picture
– https://www.projectsmart.co.uk/controlling-project-costs-
through-interactive-planning.php

Picture Time
77

What’s next
79

What’s next
80
• Are you ready to step up and share your knowledge? Be the next
MuleSoft Meetup Speakers. Feel free to approach the organizers for
more information.

What’s next
81
• Our next meetup:
– Date: April 2019
– Topic: TBD

What’s next
82
Share:
• Invite your network to join:
https://meetups.mulesoft.com/manila/

What’s next
83
• Feedback:
– Contact your organizers Janos Geronimo, Christopher Co and Ryan Anthony
Andal to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program

Meetup Survey
84
• Kindly answer:
– https://www.surveymonkey.com/r/YDQT99H

Networking time
Introduce yourself to your neighbors!

Networking time
86
Charades Game
Mechanics:
• 2 Teams consisting of 4 members
(from different companies)
• For each team, 1 person will act
and the other members will be the
ones to guess
• No speaking or making sound
effects. Only gestures will be
allowed
• Each team has a maximum of 2
mins to guess the words.
• Fastest team to guess the most
number of words under 2 mins
wins
• Guess words are part of the meet
up topic

See you next time
Please send topic suggestions to the organizer

Manila MuleSoft Meetup #4 January 2019

Manila MuleSoft Meetup #4 January 2019

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Manila MuleSoft Meetup #4 January 2019

Similaire à Manila MuleSoft Meetup #4 January 2019 (20)

Dernier

Dernier (20)

Manila MuleSoft Meetup #4 January 2019