apidays LIVE Jakarta 2021 - Accelerating Digitisation
February 24, 2021
Overcoming the 3 largest obstacles to digital transformation
Alan Glickenhouse, Digital Transformation Business Strategist at IBM
3. What is DigitalTransformation?
3
“Digital transformation is the process of shifting your organization from a legacy approach to new
ways of working and thinking using digital, social, mobile and emerging technologies. It involves
a change in leadership, different thinking, the encouragement of innovation and new business
models, incorporating digitization of assets and an increased use of technology to improve the
experience of your organization's employees, customers, suppliers, partners and stakeholders.”
Source: The Agile Elephant - http://www.theagileelephant.com/what-is-digital-transformation/
Existing
Assets
Emerging
Technology
Ecosystem
Agility
Innovation
Privacy &
Security
New Business
Models
Omni-
Channel
Cloud
AI
API Economy
Microservices
4. front-
office
middle office
back-office labor pools
multiple core legacy
differentiating
value
focus / spend
Core Systems
Client
Management
Reporting Finance
Operations Compliance
Onboarding Service
Channels
multichannel ecosystem
cognitive analytics
Re-imagined
processes
core
utility
IoT Partner
Channels
Cognitive
Engagement
Blended
Industry
Propositions
Core in
Cloud
Data & AI
Driven
differentiating
value
focus / spend
From inside-out…
force fit customer to product capabilities
(transaction driven)
… To outside-in
Manage interactions to optimize transactions
(customer driven)
Obstacle 1 – Changing Perspective
Changing perspectives from “provider-focused” to “consumer-focused” is the first major obstacle.
• Core IT systems are Provider focused – making this obstacle even more difficult to overcome
• Overcoming requires:
1) Making Digital Transformation an Executive / Corporate priority
2) Establishing roles and responsibilities in Business and IT
3) Recognizing this is an ongoing journey, not a one-time project
8. Obstacle 2 – Business Models
For example: API Marketplaces
Your Business
Your Customers
TRUST
API
Vetting
&
Onboarding
API
Marketplace
Identity
Service
$$$
Shipments Payments Other API
products
9. Drives Adoptions of APIs
Typically, low valued assets
Drive brand loyalty
Enter new channels
For Free
Facebook Login API
provides free
authentication for
any Web / mobile
app
Example:
Developer Pays
Business Asset must be of
high value to the Developer
For example, marketing
analytics, news,
Capabilities such as credit
checks
Example:
Developer Gets Paid
Provides incentive for
developer to leverage web
API
Ad placements
Percentage of revenue
sold product or services
Google AdSense
APIs pay developers
who include
advertising content
into apps
Example:
Indirect
Use of API achieves some
goal that drives business
model.
E.g., Increase awareness
of specific content, or
offerings
eBay Trading APIs
offer developers
access to trading
services extending the
reach of listings and
transactions
Example:
The Business ofAPIs - Monetization
API Monetization Understanding Business Model Options
IBM Cloud – No cost
trials, pay per use,
scale up and down
20. Getting Started
1. Executive and Business Backing
• Digital Transformation needs to be understood and prioritized by high level executives and line of business
• Lack of executive or business buy-in will result in a technology implementation with no/little impact on the business.
• Leadership absolutely must participate and back the initiative.
2. Establish a strategy and goals
• Understand why you are executing a Digital Transformation strategy
• Set Goals for the initiative with time frames and reporting metrics
3. Commitment to Funding, Roles, Responsibilities, and
Resources
• Funding to create API Products
• There will need to be resources dedicated to the initiative to enable Digital Transformation success.
• Enable enough key resources to make governance effective.
4. Get the Message Out
• Involve some people skilled in formal communication and education
campaigns.
• Do some evangelist work
• The core team’s role(s) must be understood and propagated
• Collect and Publish Metrics
23. Alan’s Articles, Blogs, Papers, andVideos…
https://community.ibm.com/community/user/blogs/alan-
glickenhouse1/2021 (change year for each year’s content)
API Economy and API Management Basics:
•. What is an API? and What is the API Economy?
• What is API Management?
• Alan Tells All About APIs (old video – no longer available)
• IT Uncensored – What is API Management? (video)
• What are businesses doing with APIs and why are they doing it? (video)
• API Economy Drivers
• Happy API Year! (from 2017)
• I Already Have Partners Accessing My Services. Why Should I Use APIs?
• Should Business APIs Replace EDI?
• Providing APIs or Managing APIs – There is a Big Difference
• Don’t be Afraid of Public APIs
• Does size matter? (for your business to participate in the API Economy)
• API Connect Video Series: API Economy – What’s happening and where
is this going? (Part 1) and (Part 2) (video)
•APIs and Events – Recognizing Opportunities Instead of Reacting to
Problems
•The Biggest Impediment to API Economy Growth is…?
• Is Two-Speed (Bimodal) IT a Good Thing or a Bad Thing?
Digital Business / Digital Transformation / Cloud Integration:
• Becoming a Digital Business – Is API Management Enough?
• Digital Transformation – Becoming a Digital Business
• Digital Business and APIs – Need to See the Forest and the Trees
(article)
• Digital Business Value when Combining API Management and Istio
• Digital Transformation Requires Integration Modernization
• Integration Modernization Requires Good Parenting
• Why Become a Digital Business?
• How Systemized Innovation Enables Digital Transformation (article)
• History of IT Constraints – What Might Constrain Digital
Transformation?
• Creating A Digital Ecosystem – Past, Present, and Future
• Business APIs – The Secret Sauce in Successful Digital Marketing
(article)
• Overcoming the 3 Largest Obstacles to Digital Transformation
(article)
• Covid-19 and Cloud Integration 1 – Moving Forward
• Covid-19 and Cloud Integration 2 - Immediate Actions
• Covid-19 and Cloud Integration 3 - Shopping and Supply Chains
• Covid-19 and Cloud Integration 4 – Supporting Your Customers
• Covid-19 and Cloud Integration 5 – Government Scenarios
• Covid-19 and Cloud Integration 6 - Service businesses, Recreation,
Entertainment, Travel, and Risk management
• Covid-19 and Cloud Integration 7 - Call to Action
• Good Integration Patterns Never Die, You Just Add More
24. Alan’s Articles, Blogs, Papers, and
Videos…
Business and Value
• Why Your Business Needs APIs (and Why Your APIs Need IBM API Connect)
(white paper) + Blog
• Why Choose IBM API Connect?
• API Monetization – What Does It Really Mean?
• API Connect Video Series: API Monetization (video)
• API Monetization Understanding Business Model Options (white paper) + Blog
• Gartner Once Again Recognized IBM as a Leader in 2021 Magic Quadrant
(2021)
•Gartner Once Again Recognized IBM API Connect as a Leader in 2019 Magic
Quadrant (2019)
• IBM’s API Management Undisputed #1 in Market Share – Again (2019)
• IBM’s API Management Undisputed #1 in Market Share (2018)
• Analyst Firm Lists IBM API Connect as an API Management Leader (2021)
• Analyst Firm Lists IBM API Connect as an API Management Leader (2018)
• Analysts Cite IBM as a Leader (2016)
• What is the ROI for API Connect? – Forrester TEI Study Demonstrates
Economic Benefits
• Forrester TEI Study Results Show 674% ROI
• RFP Template – Assistance in Choosing an API Solution Partner
• IBM API Connect: Powering the New Channel
• Do APIs Cause Channel Issues and Loss of Direct Customer Interaction?
• State of the API Economy (video interview)
• State of the API Economy 2021
• State of the API Economy – January 2019
• How to Get the Business to Participate in an API Initiative
• How IBM API Connect Helps Royal Mail Group Deliver
• The Business of API Marketplaces (article)
• Now Trending: API Platform Economy (article)
• Ecosystem and Marketplace Strategy with Alan Glickenhouse of IBM (interview)
Strategy, Governance, and Best Practices
• Creating an API Economy Strategy
• Creating an API Economy Strategy – short version (video)
• Implementing Governance of an API Initiative
• Organization and Governance of API Initiatives
• What are the Recommended Roles for an API Initiative?
• What is the Recommended Organizational Structure for an API Initiative?
• Real World Experiences with API Centers of Excellence (CoE)
• Recommendations for an API Economy Center of Excellence (white paper) + Blog
• API Center of Excellence and Governance (interview)
• API Economy Best Practices (white paper) + Blog
• API Connect Video Series: API Economy Best Practices (video)
• Identifying Good Candidates for APIs
• The 7 Biggest Mistakes Companies Make on their API Initiatives
• GDPR Considerations for Integration and the API Economy
• API Management Across Multiple Lines of Business (LoBs)
• API Versioning – Best Practices (and not so great practices)
• API Connect Video Series: API Use Cases (video)
• API Economy – 4 Business Drivers and 7 Use Case Categories – Series Overview
• API Economy Business Drivers: #1 – Speed
• API Economy Business Drivers: #2 – Reach
• API Economy Business Drivers: #3 – Innovation
• API Economy Business Drivers: #4 – Domains
• API Economy Use Case Identification: #1 – Mobile
• API Economy Use Case Identification: #2 – Social
• API Economy Use Case Identification: #3 – Data
• API Economy Use Case Identification: #4 – Other
• API Economy Use Case Identification: #5 – Partner
• API Economy Use Case Identification: #6 – Public
• API Economy Use Case Identification: #7 – IoT
• API Products – Who, What, Where, When, Why, and How
• Beating (or Catching Up with) the Competition through APIs
• The API Economy Journey Map: How Are You Doing?
• API Economy Journey Map FAQs
• Discussing Your API Initiative With the Legal Department
• Why Isn’t My API Achieving the Desired Results?
• Changing Culture – How Committed Are You? (article)
25. Alan’s Articles, Blogs, Papers, and
Videos…
Industry
• FAQ – Which Geographies and Industries are Most Advanced in the API Economy (article)
• API use cases for every industry
• APIs for Aerospace and Defense Blast Off
• What’s driving APIs in Automotive?
• Identifying API Use Cases: Automotive (white paper) + Blog
• Banking on APIs
• Banking on APIs – part 1 and part 2 (podcast)
• PSD2: Banking and the API Economy (video panel discussion)
• Q&A with the Head of Technology at Open Banking Ltd.
• Identifying API Use Cases: Banking (white paper) + Blog
• Drilling into API usage in Chemical and Petroleum
• APIs for CPG – Managing Bathrooms to Supply Chains
• Learning your ABCs using APIs – APIs in Education
• No Shock the Electronics Industry is Charged Up about APIs
• Financial Services – Planning to Retire on APIs
• Identifying API Use Cases: Life Insurance / Financial (white paper) + Blog
• Government APIs – Do More with Less
• Identifying API Use Cases: Government (white paper) + Blog
• Healthcare APIs – A Cure to Accessing Healthcare Systems
• Healthcare Providers – A Prescription for APIs
• Identifying API Use Cases: Healthcare / Life Sciences (white paper) + Blog
• Healthcare and APIs (podcast)
• Sample API Use Cases for Insurance (article)
• Creating an Insurance API Platform (article)
• APIs for Insurance – Avoid the Risk of Falling Behind
• Identifying API Use Cases: P&C Insurance (white paper) + Blog
• Legal vs IT: Usage of APIs throughout the Business (article)
• APIs: A Prescription for Challenges in Life Sciences
• Building APIs for the Manufacturing Industry
• Media and Entertainment – Hooray for APIs!
• Unearthing API Use Cases in Metals and Mining
• Today’s Special: APIs for the Retail Industry
• Identifying API Use Cases: Retail (white paper) + Blog
• ReshAPIng Cities – Using APIs to Build Smarter Cities
• Software Industry API Use Cases – Eating Our Own Cooking
• Telecom and APIs – Now We Are Talking
• Identifying API Use Cases: Telecommunications (white paper) + Blog
• APIs are Taking Off In Travel and Transportation
• APIs for Utilities – Let’s Do Something About the Weather!
• API Industry Standards and Regulatory Requirements
Architecture, Technology, and IBM Products
• Introducing API Connect (video)
• APIs and SOA – Better Together (video)
• API Connect Video Series: APIs and Services What’s the difference? (video)
• Positioning APIs and Services – Let’s End the Confusion!
• How To Get To Two Speed IT
• An ESB is Not API Management
• Is a Combined ESB and API Management a Good Idea?
• IBM Brings Multiple Integrations To a Single Platform; Focuses on Optimizing
Integration for the Multi-Cloud Enterprise (interview)
• Using APIs and Microservices as a Fast, Low-Cost and Low-Risk Innovation
Engine (article)
• API Connect Video Series: IOT – Focus on Security (video)
• Internet of Things APIs – Focus on Security
• Analytics: The Icing on Top of Your API Management Cake
•Clearing Up Misconceptions About APIs and Microservices
•Which Comes First, The API or The Service?
•Do Not Be Afraid of API Initiative SUCCESS
•Integration Architecture Decisions – APIs, Services, and Microservices
•Use API-First Design to Address Multi-Cloud Architectures (article)
•How Do You Ensure API Quality?
• API Connect V2018 Whitepaper Now Available
• Ping Identity and IBM Partner to Protect Against API Cyberattacks
• IBM API Connect Wins 2019 iF Design Award
• Integration Monitoring – Do You See the Trunk or the Entire Elephant?
• Today’s Biggest IT Constraint – Break Through It!
• Focus on the API Developer (article)
• Principles for API Security (white paper) + Blog
• Plan Ahead! Don’t Build an API Superhighway into a Cul-de-sac
Editor's Notes
- That 70% of digital transformation projects fail
- And they fail because of a lack of integration quality
- At IBM, our contrarian view, one that many integration vendors have yet to realize, is that going fast without the right approach, an approach guided by real world data, by your own operational data in a closed loop that is continuously helping you improve the quality of your integrations using automation and AI, will simply get you to the wrong place faster
- The iPaas vendors talking about automation are going to help you get to the wrong destination faster because their strategy doesn’t consider a closed loop approach, doesn’t consider how to use your operational data and only thinks about a single style of integration
- [PROMPTING QUESTION]: Are you seeing success in your digital transformation projects, and why?
- [PROMPTING QUESTION]: Does your integration approach utilize your company’s own operational data to help improve your integrations?
Agile integration is much broader than just a technology conversation. It affects it requires changes in the architecture of approach and also reaches back into the organisation itself in terms of how people are organized and what processes and methods are used. We will delve into each one of these areas in some detail but at a high level a few things should stand out.
We are aiming to enable a broader audience to be able to take part in the creation of integration.
We want to move to architectural approaches that provide a more fine-grained and componentized approach to the deployed artefacts.
We want to leverage recent advances in technology, currently especially in relation to containerization, that enable a more consistent approach to deployment and management of components across different capabilities.
For the architects in the room are pictures of course worth 1000 words and this diagram aims to show how enterprise scale integration has evolved over recent decades. Somewhere probably in the first couple of columns Will be where you are today and somewhere in the latter two columns maybe where you would like to be. We don’t have time to go through this diagram and the concepts behind it in the detail it deserves but there are references at the bottom of the slide that you can look at later. Let’s take a quick tour through the different stages.
The first stage is typically where customers are at the tail end of a service orientated architecture program, they have implemented a centralized enterprise service bus that enables them to gain access to systems of record easily from the new more customer focused engagement applications. Of course service orientated architecture wasn’t quite that easy and and the centralized ESB and its related team of integration specialists often became a bottleneck.
The next the second stage shows the point where companies began to recognize that the reusable services they had found may have value beyond or indeed within the company boundary. This was also accompanied with a new protocol known as a rest for APIs which promised a slightly simpler way of exposing data and function. Hope your management and indeed the move into the API economy enables enterprises to collaborate more effectively with external parties and perhaps even monetise their APIs as products.
In the third stage we see that the applications are now taking advantage of modern infrastructure such as containers to write more fine-grained components that can be changed more quickly and scale more easily. We can then look down at the enterprise service bus and consider breaking that up into more fine-grained pieces, perhaps even as far as one container per integration. This enables integrations to be created and changed at a much more rapid pace and for them to take on new features in the runtime and indeed security updates much more immediately.
In the final stage we see that we have taken the opportunity to change who owns the integrations perhaps enabling application teams to build and maintain their own integration is allowing us to decentralize and scale up the number of integrations being created.
There are quite rightly questions to be answered around how to manage increased numbers of components and how to govern the more decentralized approach, but these are questions that also need to be asked of teams moving into microservice based application implementations. These approaches are powerful, but I’m not necessarily suited to all circumstances.
15
We speak often about exposing functions and data synchronously using APIs. However, a huge amount of integration is done asynchronously, using messaging products like IBM MQ. That trend continues, and indeed takes on a new lease of life when we look at what the requirements are from a microservices application. Microservices by design should be as independent from one another, and from back end systems as possible. If a microservice component calls another component using an API, it immediately has a real-time dependency on that other component’s availability, and performance characteristics. For many circumstances that situation will be acceptable in order to benefit from the simplicity that an API invocation provides. However, there will be circumstances where a microservice will want to be more isolated. This is where messaging patterns have come back into fashion, but in a new form, and indeed often a new technology. Whilst arguably much of what we are doing could be done with existing messaging capabilities such as IBM MQ, we see an increased update in event streaming technologies such as Kafka. If the systems of record can provide notifications of all the changes to their data onto an event stream topic then microservices can listen in to that topic and build a local representation of that data in exactly the for they need it. The have then completely decoupled themselves from the backend systems availability and performance characteristics. The downside of course is that they have to take on the job building that duplicate copy of the data, and it is a lot harder for them to know whether they are completely up to date from a data integrity perspective. So, going into the future, we will still see APIs as the predominant mechanism for exposing data, but we will see a significant increase in additional exposure of data through event streams.
- At IBM, we believe clients need to rethink their integration strategy
- We do agree with the integration vendors talking about automating integration work. This is definitely necessary.
- Now here’s where IBM’s approach differs to other vendors in the integration market
- We feel every integration must be closed-loop, meaning that the integration must use real-world operational data to inform the AI that is automating integration work. And that this operational data and AI training must be specific to your company, because your most important integration processes are shared by no other company, so the data that feeds and trains the AI automating your integrations must be specific to your company
- Finally, we strongly believe that the old approach of one integration style fits none is the wrong approach. Instead, we believe that each integration will frequently involve multiple styles of integration, from APIs to Kafka to messaging to iPaaS etc. This is a really scary point of view to niche integration vendors. Ignoring the fact that modern integrations are multi-style serves the niche integration vendor’s business, not yours.
- Simply put, at IBM, we feel that every integration must be automated, closed-loop and multi-style with AI informed by your company’s operational data to continuously improve
- This rethink of your integration strategy will help you integrate faster and BETTER
- This rethink must happen now because you’re going to be spending a significant portion of your IT budget on automation and integration in 2021 and you don’t want to end up in the wrong place faster; you don’t want to end up in the 70% of digital projects that fail to meet project goals. You risk that by following the guidance of integration vendors that talk about automating for speed but don’t think about improving integration quality, and doing so continuously.
Key Messages –
Successful enterprises are addressing integration challenges:
Moving from manual tasks requiring experts using an automated AI assisted approach to eliminate the skills barrier
Gaining operational visibility in a closed loop process to improve the integration lifecycle
And using the right tool for the job and sometimes multiple tools together rather than force fitting into a single mode of integration
Note to presenter – very important to emphasize that CP4I is one integrated product, not a bundle or bag of parts - focus on the whole, not the parts
Key Messages:
To assist businesses with their integration needs IBM has introduced the Cloud Pak for Integration
CP4I is a complete integration offering which supports multiple styles of integration. When you purchase CP4I you have access to all the integration capabilities. It is no longer necessary to estimate how much of each type of capability is individually required. If you see immediate need for one or two styles of integration, that is fine. You can purchase the capacity you need for these. However, you still have access to the other styles too. So, if it turns out you could benefit from an additional integration style and you have not used all the purchased capacity yet, you can just go ahead and use the other integration styles as well.
The Pak has a consistent user interface, shared asset repository and unified governance framework that works across all the integration styles.
It is built on top of Red Hat Openshift and runs on any cloud and on-premise.
The Pak also takes advantage of an Automation foundation set of capabilities that is consistent across all the Cloud Paks offered by IBM.
Specifically, CP4I includes the following capabilities:
API Management
Application integration
End-to-end security
Enterprise Messaging
Event Streaming
High speed data transfer