SOA and APIs

© 2013 IBM Corporation

SOA and APIs

Laura (Olson) Heritage, Product Manager, API Management, IBM

Claus T Jensen, STSM & Chief Architect, SOA Foundation Architecture, IBM

Session Number Here

2 2 © 2013 IBM Corporation

Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change

or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general

product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a

commitment, promise, or legal obligation to deliver any material, code or

functionality. Information about potential future products may not be incorporated

into any contract. The development, release, and timing of any future features or

functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM

benchmarks in a controlled environment. The actual throughput or performance

that any user will experience will vary depending upon many factors, including

considerations such as the amount of multiprogramming in the user’s job stream,

the I/O configuration, the storage configuration, and the workload processed.

Therefore, no assurance can be given that an individual user will achieve results

similar to those stated here.


We love your Feedback!

Don’t forget to submit your Impact session and speaker feedback!

• Your feedback is very important to us – we use it to improve next year’s

conference

• Go to the Impact 2013 SmartSite (http://impactsmartsite/com):

‒ Use the session ID number to locate the session

‒ Click the “Take Survey” link

‒ Submit your feedback

http://impactsmartsite/com


Agenda

• Enter API Management

• Myth and Hype between SOA and API

• Architectural Approaches to Defining APIs


Agenda





Businesses are evolving

Website

Smart Phone

Tablet Partners

Connected Appliances

Connected Cars

Game Consoles

Internet TVs

Trillions 2013 →

Website

Millions ~1999 - 2000

stores (800) ###s web sites

Not having an API today is like not having a website in the 1990s…

Consumers expect to access data any time across multiple devices

Companies can re-invent

interactions with customers, suppliers & partners

Explosion of potential clients

increases opportunity, risk and innovation


The Business of APIs

Grow revenues…

… While reducing overhead

“$7bn worth of items on eBay through APIs” Mark Carges (Ebay CTO)

The API which has easily 10 times more traffic then the website, has been really very important to us.” Biz Stone (Co-founder, Twitter)

“The adoption of Amazon’s Web services is currently driving more network activity then everything Amazon does through their traditional web sites.” Jeff Bar (Amazon evangelist) / Dion Hinchcliffe (Journalist)


Apps, APIs and API Mgmt…

Business Owner IT

Developer

Consumers

New business opportunities

• New markets

• Increase customers

• Enhance branding

• Competitive advantage

Extend development team

•Increase innovation

•Increase scale

Partner/supplier

alignment

Benefits

Challenges

Business strategy

Infrastructure

• Security

• Creation

• Scalability

Operational control

• Publish

• Analyze

• Monitor


APIs are Emerging Across All Industries

Energy and Utilities

Government Healthcare Transportation Retail

Banking Insurance Teleco Chemical/Petroleum Electronics


Companies Need to Become an Engaging

Enterprise

Apps

Customer

Business User

IT

Enterprise

App Developer

• Business Users want to engage Customers in new markets

• They need to Externalize the Enterprise

• They need to get Apps in front of these Customers

• Apps need APIs that Externalize the Enterprise

• App Developers use APIs

• App Developers are now

External to the Enterprise

• IT Guys need to secure, scale and support the externalized Enterprise

• Business Users and IT Guys needs Insights so they can respond to business needs

The Platform

Enterprises wants to tap into innovation from a large

community of developers, not just developers they employ


Agenda





The Myth and the Hype

Myth: API management is completely different from SOA and SOA will

bog you down

API Management SOA

• At the Approach Level: Both need a direct link to business outcomes ‒ API Management traditionally outward facing in opening new mobile channels more directly bringing revenue in

‒ SOA historically tending to be more focused on organizational transformation and architectural approach for creating

an agile business, often with a more indirect effect on the business bottom line

• At the Consumer Level: Both foster reuse and agility ‒ API Management consumers tend to be greater in number and not well known

‒ SOA consumers tend to be more well defined and smaller in number

• At the Technical Level: ‒ API Management offers easy more open use with REST/JSON approach

‒ API Management offers easier consumption and governance models

‒ SOA initiatives relied mostly on SOAP based services which are more structured and well defined

‒ SOA had a more well defined approach to governance with service management



Myth: API management is completely different from SOA and SOA will

bog you down

• All APIs are Services

• Not all APIs are good

Services

• Not all Services make good

APIs

API Management is a

Natural Extension of SOA

API Management and

Service Management are

converging for a more agile

approach both inside and

outside the enterprise



Myth 2: SOAP is Dead

• Does Anything in Technology Ever Die? ‒ Look at COBOL

• Quote from Customer: “Nothing ever dies in the banks”

• Does it still have its purposes? Yes, Perhaps, Maybe, Depends.. SOAP

is not just legacy


The Myth and The Hype

Myth 3: “APIs are always REST”

• Didn’t your mom teach you to never use always and never?

• However, if you are going external and trying to drive adoption

REST is the love of most developers today because it’s easy

• Better suited for mobile development

• For inside the enterprise it’s beginning to be the flavor of choice as

well


What is an Web API? An web API is a public persona for an enterprise; exposing defined assets,

data or services for public consumption An web API is simple for app developers to use, access and understand An web API can be easily invoked via a browser, mobile device, etc.

What Value Does an Web API Provide? Extends an enterprise and opens new markets and channels by allowing external

app developers to easily leverage, publicize and/or aggregate a company’s assets for broad-based consumption

What “assets, data or services” are exposed via an Web API?: Product catalogs Phone listings Insurance cases Order status Bank loan rates

Lets Further Define the World of APIs

External

App Developer


Great…but what is SOA?

A repeatable business task –

e.g., check customer credit; open new

account

A Service

A way of thinking about your business through linked services and the

outcomes that they bring

Service Orientation

Service Oriented Architecture (SOA)

An business-centric architectural approach based on service

oriented principles


API Management Tendencies are Adopted Across

the Board From Inside to Outside the Enterprise Creating a New Era Platform

• Today Customers Rapidly

Adopting REST Internally

• Want the Same Self-Service

Control Model and Control as

external API Management

• Want the fast innovation across

all areas of business

• Developers like REST better then

SOAP

• Taking their SOA to the Next

Level

Enterprise

APIs

Partner API

External API


… and SOA Principles are at the Core of New Era

Platform Initiatives

1960- 1990- 2010-

Time

Reach

Transaction Systems

Mainframe, IMS and CICS

WebSphere, Information Management

New Era Platforms

Web, e-business and SOA

Mobile, Cloud, Big Data


Partners Suppliers

Developers Customers

APIs

Apps Patterns

Cloud Services

… and needs to integrate more and more things

2005: Connecting and mediating in an IT

transactional context

2010: Connecting and mediating e2e processes

2015: Connecting and mediating people,

devices, Cloud, ….


The Myths and The Hype

Myth 4: “API management is SOA governance rebranded”

• API Management - APIs Are a Product Therefore

Need to Be Managed Like One ‒ Need Business Model for Each API (Free, Developer

Pays, Developer Gets Paid, etc)

‒ Need a Marketing Plan

‒ Need Legal Reviews

‒ Need Analytic Reports Reporting back to the Business

‒ Need to define developer management strategy

‒ Need to be very rapid in response to market

• SOA Governance – Presides over entire enterprise ‒ Establishing Organizational Transformation

‒ Enterprise Business Vision and IT alignment

‒ Service Development Lifecycle

‒ Service Portfolio Management

‒ Change management

‒ Procurement of resources

‒ Longer process

• API management is a natural extension of SOA

governance



Myth 5: “No governance is needed with API management, this allows

companies to innovate faster”

• Good Luck with That!

• Remember External APIs are a product and your

company’s external persona

• Some form of governance is necessary

Wild Wild West



Myth 6: “APIs are not versioned”

• That’s like saying you don’t need to change a

baby’s diaper

• They are versioned and you need to manage

the change and protect your consumers ‒ Don’t expose minor version changes to the

consumers. You don’t want it to appear that you are

changing your APIs on them all the time. They

won’t build a business on your APIs if you do.

• Remember APIs are a product and your

company’s external persona. Version wisely!


Systems of interaction provide lifecycle management across



• Myth: “You only need one ‘bus’ ” ‒ We have a different opinion, gateways and integration buses fulfill importantly

different topological roles. With that said, some use cases require only a

gateway, other use cases only an integration bus and yet others require both

• Myth: “You don’t need to integrate your API management solution with

any other middleware” ‒ If not, then how are you going to share metadata about available data,

services, endpoints etc.? And how are you going to manage and enforce

policies all the way from the point of engagement to the point of record?


Agenda





Architectural approaches to defining APIs

• APIs are an extension of existing service integration and creation ‒ APIs can be aggregated from multiple existing services

• APIs are being created out of non-SOA assets ‒ The API itself is nicely defined, but its realization is “ad hoc”

• APIs are a technical veneer on existing resources ‒ There is no particular architecture or design behind the APIs, they are created

ad hoc for point use, essentially pushing EAI approaches into the API space

• New Engaging Enterprise APIs are created from scratch ‒ Particularly relevant where the APIs represent an expansion of previous

business scope (Amazon’s merchant API is one such example, it was built for

API purposes from the start); APIs are created as a business approach to

reach new markets


Business approaches to defining API’s

• Internal use for driving agility ‒ Focus: Agile end-to-end processes

• External business partner use ‒ Focus: Integration existing ecosystem

• External use for capturing new markets and driving adoption ‒ Focus: Extending ecosystem outreach

• Both internal and external use ‒ Focus: Holistic API management strategy enterprise wide


Architectural approaches to defining API’s

• APIs are an extension of existing service integration and creation ‒ Targeted for internal and/or external use

‒ Designed for reuse by many apps

‒ Realized via connecting to an (Enterprise Service) Integration Bus

‒ May aggregate across internal and public cloud services, but in most cases

composition is handled in the (Enterprise Service0 Integration Bus

‒ Typically enterprise class QoS



• APIs are being created our of non-SOA assets ‒ Targeted for internal and/or external use

‒ Designed for reuse

‒ Realized directly from packaged apps, cloud services, existing backend

systems etc., using adapters available within the API environment

‒ Aggregation, when needed, happens within the API managed environment

‒ QoS typically inherited from the backend realization



• APIs are a technical veneer on existing resources ‒ Targeted for internally developed mobile apps (typically driven by getting a

mobile app released)

‒ Not designed for reuse

‒ Realized as a thin veneer on top of existing systems

‒ Aggregation, when needed, happens within the API managed environment

‒ QoS inherited from the backend realization



• New Engaging Enterprise APIs are created from scratch ‒ Targeted for external use, aiming solely at an ecosystem beyond the

enterprise

‒ Maybe designed for reuse

‒ Implemented created from scratch (often using big data, analytics, social

technologies)

‒ No full-fledged composition, but leveraging various connectors to data

sources and transformations as needed

‒ QoS can vary widely, often the requirements are much lower than for classical

enterprise systems (“good enough” approach)


Summary

• The concepts of SOA and APIs are highly synergistic

• APIs provide SOA with a way to reach beyond the controlled

environment of the enterprise

• SOA provides APIs with acceleration and proven design principles

• Defining a strategy for how to merge SOA and API management will be

important (long term) to most enterprises…

• … and this does include a middleware strategy for how to source and

integrate gateway capabilities and integration bus capabilities



Legal Disclaimer

• © IBM Corporation 2013. All Rights Reserved.

• The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained

in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are

subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing

contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and

conditions of the applicable license agreement governing the use of IBM software.

• References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or

capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to

future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by

you will result in any specific sales, revenue growth or other results.

• If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete:

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will

experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage

configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

• If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete:

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs

and performance characteristics may vary by customer.

• Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM

Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server).

Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your

presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in

your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International

Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

• If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete:

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

• If you reference Java™ in the text, please mark the first use and include the following; otherwise delete:

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete:

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

• If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete:

Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and

other countries.

• If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete:

UNIX is a registered trademark of The Open Group in the United States and other countries.

• If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete:

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of

others.

• If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta

Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration

purposes only.

http://www.ibm.com/legal/copytrade.shtml