This document summarizes a presentation about APIs and microservices. It discusses how digital companies have adopted microservices at scale due to their business models and technical foundations, while traditional enterprises face more challenges. It then demonstrates IBM API management and StrongLoop products, showing how they can help companies expose and manage APIs internally and externally. The presentation concludes by announcing a new IBM product that integrates API management and development capabilities.
4. A global award that recognizes the
success of IntegrationWorks enterprise
integration transformation project with
New Zealand Racing Board.
The solution accelerated digital
transformation, revenue channel increase
and enhanced customer experience
Winner of
IBM Beacon Award 2016
Outstanding Middleware Solution
6. Agenda
7.10 – Welcomes
7.30 – Approaching the API Economy
8.10 – Refreshment Break
8.20 – API Technology and Demo
9.00 – Question & Discussions
9.15 – Wrap up
9.25 – Networking and meet the
IntegrationWorks team
Evolving API Reference Architectures
Fueling external innovation - IBM API Management
Supporting internal agility - IBM StrongLoop
Ian Richards - MD, IntegrationWorks AU
David Bate - VP Hybrid Cloud, IBM Asia Pacific
Bob Morton - QLD State Manager, IBM AU
Ian Vanstone, CTO, IntegrationWorks
APIs for business
API delivery approaches
Laying the foundations for API First Microservices
11. Focus on business model, target partners
Known Targeted Partners
Existing
product/service
New
product/service
New market
API supports
product/service
or
API is the
product/service
Low
effort/ROI?
Medium
effort/ROI?
Major
effort/ROI?
Business model
Per product/service/API
Not per business
12. 1. Learn lessons projects
2. Well planned programmes
3. API First
Approaches
Speed & Agility
Integration & Scale
Core
Enterprise
Digital
EcosystemFast
Speed
Steady
Speed
14. Organisational change and enablement
• Broad education and engagement
• Engage business/commercial early and ongoing
• Engage legal, marketing, brand early and ongoing
• New roles, new teams, different ways of working
• Update Op Model
• Talent source to help define, upskill, and deliver
• Events
Well planned programmes
IT & Technology
• API Governance and Guidelines
• Continuous Delivery
• API/Data ownership
• Partnership relations and API
governance and release cycles
• New architectural components,
patterns and technologies
• Runtime and delivery
• More than an API Management
platform
Funding roadmap
• Business engagement, partner engagement,
internal engagement – and more below
• Ongoing funding beyond initial project
15. Decentralised architecture
Decentralised integration
Breaking monoliths
Changing the balance of Buy Vs Build
API First
System/App level:
• All features and functions can be accessed and controlled by APIs
• All APIs are designed to be exposed externally
Enterprise level:
• All products and services can be accessed and controlled by APIs
(e.g. browse, buy, personalise, interact)
WHAT?HOW?
Microservices
17. Microservices – it’s more than code
Traditional shared services based organisation Microservices enabled organisation
Project model Temporary teams built to fit funding cycles (e.g.
Annual plan)
No projects, backlog driven
(Or backlog-driven programme/project model)
Teams great at chunking work
Requirements Coarse grained outcomes Granular outcomes
Design Large documents spanning shared service teams Emergent / iterative
Design and test driven
Code/Build/Deploy Services highly coupled Decoupled
Test High documentation High automation
Release Coupled to deploy
Once per project
Decoupled from deploy
Frequent
When features ready
Operate/Scale Manual Control/Monitor/Scale of platforms Auto Control/Monitor/Scale of services
Decommission Complex, costly
Avoided
Rising keep-the-lights-on cost
Hot swap services in/out
20. Text
Digital companies/divisions/teams
Multi-year sustained high growth
Colossal scale
Minimal legacy
High ratio IT investment, high appetite for risk
around developing new practices
Reliant on emergent design - unable to utilise
long plan cycles due fast evolving product
sets, customer base, or market
Traditional IT architectures are unable to flex at
colossal scale – technically or financially
Not restrained by large COTS or
otherwise inflexible systems/monoliths
Does your business fit the mould?
21. Agile funding mechanisms
Highly flexible organisational model
Granular Product Management practices
Able to govern flat, decentralised, smaller teams
Mature Continuous Delivery practices
Mature operational practices and systems
Does your business have the foundations required?
The Foundations for Microservices
22. Able to leverage and develop new technologies
Able to adopt and manage decentralised data stores
Adequate access to IT talent
Able to manage the border between traditional delivery and microservices delivery
Able to secure a larger and evolving attack surface
Does your business have the foundations required?
The Foundations for Microservices
23. Yes
Huge benefits
Agility from flexibility
Foundations in themselves are often highly valuable
Be great at continuous Delivery
Adoption risk/cost is lowering
Growing talent pool
Growing access to IP, use cases,best practices
Growing numbers of easier-to-consume tools
So is there any point in traditional enterprises looking into microservices?
Yes
Yes
Upskill in order to make informed decisions on alignment or adoption
Assess ongoing
Plan and execute the IntegrationWorks Foundations for Microservices
Manage risk – scalable budgets, delays/impacts, legacy creation….................
Act
28. APIs and Managed APIs
”Unmanaged” Managed
Security Focused on connection/message Plus delegated authority
Plus social sign-in
Control, SLAs, traffic shaping By API operation or server By API operation, plan, partner, app
Monetisation Hard Easier based on per app data
Internal analytics By API operation or server
Export logs/reports
By API operation, plan, partner, app
Beautiful visualisations/graphs
APIs
External analytics None By API operation, plan, app
Beautiful visualisations/graphs
APIs
Developer Portal None OOTB feature
Test tools None OOTB for internal and external developers
Code generation and SDKs None OOTB feature
Community Management, etc None Internal and external org management
Forums
34. IBM StrongLoop Components
on cloud Bluemix Bluemix Dedicatedon premise Bluemix Local
Supporting internal agility
Start with code Or start with data/APIs Manage
Live demo
API First microservice creation in
one easy minute
35. IBM API Management Components
Developer Portal API Manager Management Console
Define and manageAPIs
Explore API usage with
analytics
ManageAPI user communities
Provision system resources
Monitor runtime health
Scale the environment
API Gateway
Enforce runtime policies to
controlAPI traffic
Welcome to the API Portal
Explore API documentation
Provision application keys
Self-service social experience
Fueling external innovation
on cloud Bluemix Bluemix Dedicatedon premise Bluemix Local
Live demo
Expose APIs to partners in
one easy minute
36. Announcing IBM API Connect
Create, Secure, Manage, Run
Integrates IBM StrongLoop and IBM API Management with a built-in gateway
38. Invite us in to talk about your business
APIs and Microservices
Enterprise integration, Hybrid cloud integration
Any kind of integration
Keep in touch
§ www.integration.works
§ Our Whiteboard Blog
§ Join our mailing list
§ Follow us on LinkedIn