MuleSoft Meetup - 7.pptx

6 July 2022
Manchester MuleSoft Meetup Group
API Specification Automation via Platform APIs and
7 Steps to Achieving Effective API Insights

2
● Introductions
● API Specification Automation via Platform APIs
● 7 Steps to Achieving Effective API Insights
● Quiz
● Networking time
Agenda

3
●About the organizer:
○ Akshata Sawant
○ Meghana Prasad
○ Terry Lockwood
●About the sponsor:
○ EPAM
○ Slalom
○ MuleSoft
Introductions
A SHOW OF HANDS:
Who is new to this Meetup?

● Australian born, dual Oz/UK national
● 25 years total experience
● Worked globally across Asia/Pac, EMEA, US,
Africa and places in-between such as a few
pacific islands that are barely visible on a map!
● 25 years in systems integration across every
tech stack imaginable – Oracle, IBM, APIGEE –
and MuleSoft
● Been using MuleSoft for nearly 6 years –
dropped into it at the deep end a client wanting a
POC ! Went from there 
● Enjoy riding the elevator from C-Suite to Engine
Room and always having my hands on the tech
About the Speaker
4
Steve Clarke, Practice Director UKI – MuleSoft & Integration – Slalom

6
• Anypoint Studio 7.12 with Mule Runtime 4.4
• Anypoint Flex Gateway : API Gateway for APIs running anywhere
Announcement

Using Postman Collection
API Specification Automation via
Platform APIs

Glossary
● API Specification: API skeleton/ Structure of request, response.
● Design Center: Anypoint Design Center is a development environment. API Designer
enables you to create API specifications in several modelling languages and to create RAML
API fragments.
● Anypoint Exchange: Where you publish that API Specification to create an Exchange Asset
so that anyone in the organization can find, consume, and reuse them.
● Platform APIs (Anypoint): RESTful web services exposed by Anypoint Platform.
8

Anypoint Platform APIs
● Anypoint Platform UI is backed by REST APIs to expose its management capabilities.
● Also known as Anypoint Platform APIs, public APIs, MuleSoft’s Platform APIs
9

Sample Use Case - Login
Via Platform API
Via UI

Anypoint Platform APIs
Platform
APIs
Access
Management
Design
Center
Object Store
API Manager
Runtime
Fabric
Cloudhub
Design
Center
Importing API
Specs
API Spec Import
Exchange
Dependencies
Publish to
Exchange
Creating or
deleting
project(s)
Branch
Management
Design Center Platform APIs

12
● Automate API Specification lifecycle via Platform APIs.
○ Uploading/ Importing a Spec in Design Center, manipulating files/ folders/ dependencies, publishing
to Exchange etc.
API Specification Automation

Use Case 1
Creating a project, adding files and publishing to Exchange.

Use Case 2
Importing an API Specification and Publishing to Exchange.

15
Pre Requisites
Login Profile Information
API Specification
Automation
via Platform APIs
Access Token Organization Id
& Owner Id +
Access Token
Get the required data for calling Anypoint Platform APIs
• Access Token
• Organization Id
• Owner Id
Username & Password/
Connected App

17
● Branch: Acquire write lock, release write lock, create a branch, delete a branch, clean branch,
branch status, list branches, check lock status etc.
● Project: Create a new project, Create fragment, Import API Spec
● File(s) & Folders: Add/ Update file content, Get file/ folder structure, get file content, move or
rename file/ folder
● Dependencies: Add, Update or delete dependency
● Publish: Publish to Exchange, Publish to Platform
● Delete: Delete a file or folder, delete a project, delete an asset (Soft/ Hard delete)
More operations

18
https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/
More Platform APIs

Questions/ Suggestions/ Recommendations
Q&A

Slalom is a modern consulting
firm focused on strategy,
technology, and business
transformation.
S T R A T E G Y
Redefine what’s
possible
Go beyond the expected. We help you move confidently through
ambiguity and risk, focus on your customer needs, and deliver
sustainable business value.
We analyze,
architect,
and co-create
Learn from your data, create incredible digital experiences, or
make the most of new tech. We blend design, engineering, and
analytics expertise to help you build the future.
T E C H N O L O G Y
Enact lasting change
New technologies. Shiftingcustomers. Industry disruption.
Business moves fast, and we specialize inworking through change
with you.
T R A N S F O R M A T I O N

Personal
connection
at global
scale
©2022 SLALOM. ALL RIGHTS RESERVED. PROPRIETARY AND CONFIDENTIAL.
Atlanta
Austin
Boston
Charlotte
Chicago
Columbus
Dallas
Denver
Detroit
East Bay
Fort Worth
Hartford
Houston
Kansas City
Los Angeles
Minneapolis
Nashville
New Jersey
New York
Orange County
Philadelphia
Phoenix
Portland
Raleigh
Sacramento
Salt Lake City
San Diego
San Francisco
Seattle
Silicon Valley
South Florida
St. Louis
Tampa Bay
Washington DC
Westchester/
Southern CT
Calgary
Montréal
Toronto
Vancouver
N O R T H A M E R I C A
United States
A S I A P A C I F I C
Australia United Kingdom
Build Center
Japan
E U R O P E
Germany
Canada
London
Manchester
Munich
Tokyo
Melbourne
Sydney

Expertise
that
powers
innovation
• MarketingCloud
• B2B Commerce
• Customer360 platform
• Integration/Mulesoft
• PublicSector
• RevenueCloud
• Sales Cloud
• Service Cloud
• Analytics (Tableauand Einstein)
• B2B Commerce
• B2C Commerce
• CommunityCloud
• Customer360 Platform
• Field Service Lightning
• Heroku
T O P 1 0
C O N S U L T I N G
P A R T N E R
• B2B Commerce
• B2C Commerce
• ConsultingEcosystem
• ConsumerGoodsCloud
• Field Service Lightning
• FinancialServices
P A R T N E R
A D V I S O R Y
B O A R D
• HealthCloud
• MarketingCloud
• Pardot
• Sales Cloud
• Services Cloud
• Tableau
N A V I G A T O R
E X P E R T
As aleader in every area ofthe Salesforce
ecosystem we help ourclients connect
the dots toachieve the extraordinary.
• MuleSoft
• Maps
• MarketingCloud
• PublicSector
• RevenueCloud
• Sales Cloud
• Service Cloud
• Vlocity
service cloud
sales cloud marketing cloud community cloud platform
financial services
cloud
health cloud einstein B2B commerce cloud
C360 audiences
B2C commerce cloud
maps
voice
quip
loyalty cloud
revenue cloud consumer goods cloud
communications cloud
experience cloud
CRM
enterprise architecture
field service lightning
datorama
interaction studio
chatbots
apps
C LOUD L EADERSHIP

Capability Highlights
Integration and API Strategy
Working with you to understand and frame the Integration and Connectivity
challenges within your organization and shaping an API led strategy via MuleSoft
that will lead to rapid success.
MuleSoft Accelerators
Establishing the foundational People, Process and Technology capabilities
needed to support and accelerate your API ecosystem with MuleSoft at the core
MuleSoft Platform Delivery
Providing Architectural, Build and Delivery services to rapidly accelerate your API
journey with MuleSoft and unlock value across your enterprise.
API and Platform Assurance
Capabilities and services designed to enable your MuleSoft API lifecycle and ensure
your are continually delivering the highest quality API’s for your business, customers
and partners.
API Insights and Optimization
Gaining insight into the operational effectiveness of your platform investment and
leveraging core MuleSoft and Third Party solutions to unlock and optimize value in
your API ecosystem.
Slalom is Focused
on MuleSoft
We define integration strategies, deliver solutions and are considered thought
leaders in the spaces of Enterprise Integration, Application Programming
Interfaces, Platform-as-a-Service and Microservices. Slalom has implemented
MuleSoft across an array of diverse customer use cases ranging from
ERP/CRM Integration, Legacy Modernization, Cloud Adoption and Data
Synchronization through to Customer 360 initiatives.
We take considerable pride in not only launching new customers on their
MuleSoft journey, but also accelerating existing MuleSoft customers derive the
most value from their platform investment to support their business.
85+
MuleSoft projects
completed
80+
MuleSoft
certifications
70+
MuleSoft
practitioners
40+
Slalom offices
worldwide
#4
MuleSoft Partner in
North America

7 Steps to Effective API
Insights
So, what’s the problem ?
1
24

API’s and KPI’s – Vicious vs Virtuous evolution
API’s can be equated to a ‘currency’ in an organisation. To make that currency of value,
one needs to provide a ‘direction of travel’ in measuring progress that is ‘virtuous’.

Insights
What’s in a metric ?
2
1
28

29
A measure of value
Meaning
Tied to a business outcome –
helps move the needle
forward

As an example, a recent project where a strong C4E and Platform Insights were combined
over time achieved the following outcomes:
30
Understandable
Recognised
Meaningful
Clearly understood
Has a value
Can be sourced or easily derived
Can form the basis of one or more POV
Measurable
Accessible
Choosing the right metrics to measure
Can be tied to Operational benefits
Can be tied to business objectives
Tied to ways of working or project delivery
Can drive tangible
outcomes
Minimal effort to expose
Ideally natively obtainable

What Metrics might we care about ?
API Reuse
Number of Users
Governance Gaps
(Categories, Tags,
Domains)
Number of API’s
vCores Usage
Assets By Type
Active Personas
Total Development
Time
API Development
Time
Developer
Throughput Average
Rating of
Assets
Number of
Applications
By Status
Speed to
Onboard
Consumption
Chargeback
Operations Consumer Metrics
Savings from
Reusability
API Usage
Across
Domains
Defects By
Stage
Cost
Reduction
API Usage
Across
Domains

Insights
Align your metrics to outcomes
3
2
1
32

API Metrics – Mapping the journey
KPI’s
Metrics
Objectives

34
/
/
/
/
/
Aligning metrics to outcomes
/
/
/
/
/
/
/
/
/

Insights
Apply your metrics in practice
4
3
2
1
35

Applying Metrics in Practice
Focus on the “why”, the “how” then becomes more transparent
Tying to business outcomes or
behavoural needs, such as
Operational Impacts, will ensure
longer term API value.
Connect To Business Goals
How often you capture metrics can make a
real difference to their effectiveness. The
older they are, the less insightful they may
be.
Establish Frequency
Absolute values such as Static Metrics are
helpful to be sure, but real insight comes
from understanding impact over time. Think
longer term.
Track Trends over Absolute
Where business outcomes are not being
met, revise and reset. Its an iterative
process.
Always remember the target behavour.
Reset and adjust
Measuring metrics or KPI’s that have
no tangible tie into business or
operational change can be seen as
measuring for the sake of doing so.
Best to avoid !
Avoid “vanity” measures
Metrics should be readily quantifiable and
qualifiable – the metrics have greater
meaning if they can provide inherent value.
Quantify and Qualify

Insights
Instrumentation and
Visualization
5
4
3
2
1
37

View all your ESG metrics on a single dashboard
Achieving a ‘single pane of glass’
across your metrics can give you true
insight.
Therefore, your approach to
instrumentation of your metrics and
KPI’s is important.
Instrumentation

Straw Man’s View on the How…… Metrics Accelerator
Production
Monitoring
Sandbox
Events, Runtime Statistics
Logging
Basic Alerts
● For Applications and Servers
from Anypoint Monitoring
API Alerts
● Policy Violation
● Request Count
● Response Code
● Response Time
● Contract alerts
Runtime Alerts
● CPU Usage
● Deployment Failed
● Worker not Responding
● Memory Usage
● Custom Application
Notifications
● (Error notifications &
Operational Milestone alerts)
Functional API
Events
Notification
Ticketing
Elastic Stack for API Governance, Platform
Monitoring (Events) and Product Owner
Insights
Governance KPI’s
● API Policies Enforced
● Exchange Content
Completed
● Tags, Domains, Categories
assigned
● Degree of Reuse
● Domain Usage
● Deployment Velocity

Insights
Instrumentation and
Visualization
5
4
3
2
1
41
Measure
6

Step 6 – Measure Outcomes
Different points of measure in your API ecosystem can exist around People, Process and Technology
Application Platform
Application
Cloud People
API Lifecycle

Insights
Instrumentation and
Visualization
5
4
3
2
1 43
Measure
6
Evangelize
7

Socialise the
goals, the journey,
the benefits of API
Insights.
Shout the
successes!
Identify effective
means of
proactively
informing KPI’s,
SLA’s and Need
for Course
Correction
Gather feedback,
ensure its
continuous.
Measure
behavioral
change
44
Step 7 - Evangalize
People you want to care probably won’t if you don’t educate, inform, give ownership

Collect metrics when
they are generated.
Some metrics are not
available later.
Retention of metrics
helps identify
trends.
Trends show
patterns of
behavour and this
can help your
focus.
Drive a positive
feedback loop into
your ecosystem
through alerts and
triggers.
46
One More Thing….. Timing and
Retention

Example #1: Measuring Usage of the Platform
8
• The What ?
1. Organisations and Business Groups – who
are your consumers ?
2. Number of reusable assets on Exchange
3. Total number of reusable API’s
4. Registered or active users of your platform
by type, role, business group, etc.
• The Why ?
1. Understand the usage of your platform,
where its high, where its needing C4E
focus
2. Monitor asset growth over time
3. Monitor and assist usage over time – who
are your ‘customers’ ?

Example #2 : API Usage by Organization, Top Used APIs
• The What ?
• Usage by different parts of the business
• Degree of reuse by API or Category
• The Why ?
• Low reuse can give insight into how
discoverable, flexible an API
• Low reuse can help identify where consumers
are seeing gaps in your API ecosystem
• Reuse monitoring can help identify
opportunities for further business enablement

Example #3: API by Business Domain
0
• The What ?
• Breakdown consumption by domain, type and
rating
• The Why ?
• Provides insight into usage across domains
• Insight into reusability across the enterprise vs
domain specific assets
• Insight into consumer feedback to drive further
enablement

Example #4: Using KPI’s for
Governance and Quality Improvement
• The What ?
• Identify gaps in Design, Non-Functionals,
Testing, etc.
• Monitor effectiveness of standards,
principles, patterns and their implementation
• Ensure platform configurations which enforce
NFR’s are being applied (e.g. Policies)
• Ensure Exchange documentation is up to
date
• The Why ?
• Gaps in quality can affect delivery
• Gaps in Non-Functionals can expose API’s to issues
around Security, Reliability, Scalability
• Non-Categorisation of assets can affect
discoverability, reusability

Example #5: API Trending – New API’s Deployed Per Day
2

Example #6: Platform Capacity Monitoring
• The What ?
• Understand platform capacity usage and
consumption
• The Why ?
• Insight into platform consumption ensures effective
use of license
• It can also give insight into potential reuse
challenges or gaps in overall design strategy of the
API ecosystem (e.g. DDD)

Example #7: Defect Management
4
• The What ?
• Cross align API insights with incident
management insights
• Reliant on integration with your incident
management platform (e.g. ServiceNow)
• The Why ?
• Insight into Build, Test and Runtime
defects across API’s, Severity, etc.

56
● Anypoint Platform APIs can only be authenticated via username & password.
○ True
○ False
Quiz

57
● When measuring metrics, what are 2 key measures that can help achieve success in your API
landscape?
Quiz

58
● Name at least one Operational and one Consumer Metric?
Quiz

59
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: <URL of your Meetup site>
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?

Introduce yourself to your neighbor
Networking time

MuleSoft Meetup - 7.pptx

Recommended

Recommended

More Related Content

Similar to MuleSoft Meetup - 7.pptx

Similar to MuleSoft Meetup - 7.pptx (20)

Recently uploaded

Recently uploaded (20)

MuleSoft Meetup - 7.pptx