In this months meetup we discussed MuleSoft's API led connectivity strategy, API layering and how it can be applied in a real HR scenario.

1. MULESOFT LONDON
MEETUP.
AUGUST 2017

2. AGENDA.
EACH COMMUNITY SESSION WILL TYPICALLY
CONTAIN A TOPIC ON INTEGRTION STRATEGY AS
WELL AS DEEP DIVE ON A PARTICULAR TECHNOLOGY
HOT TOPIC.
JOIN IN THE OPEN DISCUSSION AMONGST FELLOW
INTEGRATION PRACTIONERS.
Learn about the monthly MuleSoft London User Community
meetups, and how to get involved.
ABOUT THE COMMUNITY
Digging a little deeper into the API led connectivity strategy
and how it can be applied in a real HR scenario.
API LED IN ACTION - HR
01
02
We’ll be running an interactive event with the meetup group
– with the promise of some MuleSoft swag!
PULSE OF THE COMMUNITY
03

3. THE COMMUNITY.
This is your chance, be part of the exciting and
dynamic world of the connected enterprise.
Share your integration experiences both
good and bad.
A safe environment to learn and share with
your peers.
Build your network and discuss a variety of topics key to
a successful application network with the Mulesoft
Anypoint Platform.
We want the community to be interactive.

4. GREAT TOPICS.
SAP Integration with Mule
We have some initial ideas on topics, but want this to
be shaped by YOU. Tell us what’s important in the
community, a huge challenge, a great achievement.
DevOps for Mulesoft
What is C4E?
API Security
Marketing the value of APIs
HR Integration
Commerce Integration
Industry 4.0
Pace Layering
Interface Monitoring and Operations
File Integration
Hybrid Integration Patterns
API Led Connectivity
MuleSoft Workday Connector
Firewalls & Connectivity & CloudHub Configurations
DevOps tool configuration with Mulesoft
RAML 1.0
ELK Solution For Mule
Moving files in the Cloud
How Mulesoft works with traditional ESBs
Anypoint Edge
STRATEGY TECHNOLOGY
IOT scenarios

5. MULESOFT MEETUPS.
Your one stop shop for all things MuleSoft meetups – future events, registration, news, photos
and much more.
Keep checking in for updates.
https://meetups.mulesoft.com/

6. MEETUP + SLIDESHARE
01. Continue to support meetup.com
02. Follow us on twitter:
@paceintegration
03. Material available afterwards on
SlideShare.

7. AGENDA.
EACH COMMUNITY SESSION WILL TYPICALLY
CONTAIN A TOPIC ON INTEGRTION STRATEGY AS
WELL AS DEEP DIVE ON A PARTICULAR TECHNOLOGY
HOT TOPIC.
JOIN IN THE OPEN DISCUSSION AMONGST FELLOW
INTEGRATION PRACTIONERS.
Learn about the monthly MuleSoft London User Community
meetups, and how to get involved.
ABOUT THE COMMUNITY
Digging a little deeper into the API led connectivity strategy
and how it can be applied in a real HR scenario.
API LED IN ACTION - HR
01
02
We’ll be running an interactive event with the meetup group
– with the promise of some MuleSoft swag!
PULSE OF THE COMMUNITY
03

8. DIGITAL DRIVERS.
Companies must embrace digital transformation in
order to stay relevant to their customers.
• Digital transformation is driving companies to
reframe their relationships with their customers,
suppliers and employees through leveraging new
technologies to engage in ways that were not
possible before.
• These new technologies - SaaS, mobile, and the
Internet of Things (IoT) - demand a new level of
connectivity that cannot be achieved with
yesterday’s integration approaches.
MuleSoft advocates adopting an API-led connectivity
approach that packages underlying connectivity and
orchestration services as easily discoverable and
reusable building blocks, exposed by APIs.
• Structure these building blocks across distinct
systems, process and experience layers, to achieve
both greater organizational agility and greater
control.
• Drive technology change holistically across people,
processes and systems in an incremental fashion.
CHALLENGES STEPS TO ADDRESS

9. API LED CONNECTIVITY.
MuleSoft definition: API-led connectivity is an approach that defines methods for
connecting and exposing your business assets.
• Microservices and the realisation of a ‘composable enterprise’
• Proposes a technology solution to enable shift to decentralised operational model.
• Promotes assets and services, scalable across geographic, technical and line of business boundaries.
API-led connectivity calls for a distinct ‘connectivity building block’ that encapsulates three distinct components:
• Interface: Presentation of data in a governed and secured form via an API
• Orchestration: Application of logic to that data, such as transformation and enrichment
• Connectivity: Access to source data, whether from physical systems, or from external services

10. API LAYERING.
Experience – access to data required in different
forms. Ease of data consumption.
Process – interact and shape the data. Perform
specific functions i.e. order status.
System – underlying systems of record. Legacy
connectivity. Exposing canonical data. Change less
frequent.

11. LAYERS WITHIN LAYERS.

12. LAYERS WITHIN LAYERS.
Any good API regardless of system, process or experience has inherent qualities that enforce good practices –
defined at a platform level.
Further discussion for subsequent meetup…
• Vital to deploy strong API security
at the edge of your API
architecture.
• Can be seen contradictory to
making API accessible and easy to
consume – it’s a balance.
• Flexible access management
technologies like OAuth and
OpenID Connect compliment API
gateway.
• Maximise API efficiency
• Allow cached responses to
common requests
• Reduce pressure on backend
resources.
• Essential to positive end-user &
developer experiences
• RAML definition
• Terms of service, privacy
statement and SLA
• Licensing (interface, code, data)
• Deprecation and roadmap
• Rate limits and uptime
• Pricing and support
CACHING LAYER CONTRACT LAYERSECURITY LAYER

13. ORG ENABLEMENT.
A “Shared Service Centre” or Centralised IT
provided many benefits…
 Single ownership of IT and Delivery
 Scalable teams
 Cost Effective Outsourcing/Offshoring
 Structured processes and SLAs
 Repeatable Artefacts
Centre for Enablement (C4E) strategy was discussed in June meetup.

14. BENEFITS OF API LED.
 IT as platform for business goals
 Developer engagement
 Predictable change
 Distributed and tailored approach
 Agility through loose coupling
 Operational visibility
Speed and measurable value through reuse.

15. HR SCENARIO.
• Our example client is implementing a new Workday HCM solution and needs to integrate
their core Joiner, Mover, Leaver (JML) process with existing systems.
• Existing systems include ICIMS (recruitment), ServiceNow (service management), and Okta
(identity management) systems along with a custom JML portal for on/off boarding
employees.
• Project drivers for simplification, self-service and reduced administration overhead.
• Longer term they want to extend to a relocation services system (for international movers)

16. HRSCENARIO. Recruiter
Employee
HR Admin
Identity Admin
Ops
Admin
• Data Silos
• Data & Process
dependencies
• Scheduled &
Sequential tasks
• No feedback
• Extending to
mover/leaver means
new build

17. HRSCENARIO.

18. HOW DO I GET THERE.
Pick a specific business
challenge to overcome.
01 START SMALL
Build to scale within line of
business or project.
03 BUILD TO SCALE
Keep measuring the outcomes to
prove longer term success.
05 SUCCESS
Measure the outcomes to
prove the value
02 MEASURE OUTCOMES
Promote value of APIs across other
areas of the business – make them the
default rather than exception.
04 MARKET APIS

19. AGENDA.
EACH COMMUNITY SESSION WILL TYPICALLY
CONTAIN A TOPIC ON INTEGRTION STRATEGY AS
WELL AS DEEP DIVE ON A PARTICULAR TECHNOLOGY
HOT TOPIC.
JOIN IN THE OPEN DISCUSSION AMONGST FELLOW
INTEGRATION PRACTIONERS.
Learn about the monthly MuleSoft London User Community
meetups, and how to get involved.
ABOUT THE COMMUNITY
Digging a little deeper into the API led connectivity strategy
and how it can be applied in a real HR scenario.
API LED CONNECTIVITY IN ACTION
01
02
We’ll be running an interactive event with the meetup group
– with the promise of some MuleSoft swag!
PULSE OF THE COMMUNITY
03

20. QUICK POLL
Objective:
Share your views on the application of API Led strategy – we’ll be handing out prizes for
for the most unique and insightful answers - mainly it’s about swag!
If you’re in consulting pick your most familiar client scenario.
Task: 3-5 minutes
Playback: 5-10 minutes
https://goo.gl/at4tCG
note: it is case sensitive

21. BACKGROUND VIDEO
What is an API or Inception movie clip
https://goo.gl/at4tCG

22. RESULTS & DISCUSSION.
Categories:
• Best alias?
• Best benefit of an API led scenario?
• Best API layering use case?
• Best answer to why not point-to-point?
We will summarise results (anonymously) and publish results for the meetup group.

23. https://meetups.mulesoft.com/london/
Next Meetup: Early October
Location: TBC
JOIN THE COMMUNITY.