realizing soa and api convergence

Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.

Realizing SOA and API Convergence

for IBM DataPower Customers


Webinar Agenda

• About SOA Software

• API and SOA Convergence

• Realizing Convergence using DataPower

• Demo

• Q & A


SOA Software Overview

• IBM Business Partner• Long history providing API and SOA

solutions in IBM enterprise environments

• Unified API and SOA Platform– One Platform for both API and SOA– Full lifecycle management– Integrated runtime support

• Rich IBM Support– WebSphere DataPower– IBM Integration Bus– WebSphere MQ– System z Mainframe


Leader - Gartner Magic Quadrant 2013 Application Services Governance

• Best Vision for:API ManagementSOA Governance

• Comprehensive and well integrated offering

• Leading market understanding

The Gartner document is available upon request.*Gartner, Inc., Magic Quadrant for Application Services Governance by Paolo Malinverno, Daryl C. Plummer, Gordon Van Huizen, August 8th 2013.


SOA.com Convergence Resources

White Paper:

SOA and API Convergence : What It Means for IBM Customers

http://bit.ly/1hx1Zmk

Recorded Webinar:

Turbo Charge DataPower to Reach Your SOA Goalshttp://bit.ly/1fWLylB


SOA.com Convergence Resources

Recorded Webinar:

API and SOA - Two Sides of the Same Coin?

http://bit.ly/1kFKFhD

Recorded Webinar:

Are APIs and SOA Converging?http://bit.ly/1eOSdtG


Key Attributes: API and SOA


API and SOA Convergence

API technology focuses on consumption of enterprise resources

• API Marketing• Analytics• Performance

Management

• Developer Engagement• Cloud Presence• Monetization• Traffic Management

SOA technology focuses on production of enterprise resources

• Enterprise Integration

• Enterprise Security• Enterprise

Standardization

• Enterprise Service Lifecycle

• Enterprise IT Reuse• Infrastructure

Reliability


Models of Convergence: “A” and “B”

Convergence Model “A” lets consumption and production grow independently of each of other. Any interaction is ad-hoc.

Convergence Model “B” favors consumption over production. Service production capabilities diminish over time.


Convergence “A” and “B” Risks

High cost, overlap, and confusion trying to run multiple management solutions and multiple runtime gateways

Loss of critical service consumption and service production capabilities, hampering new mobile and digital business strategies

Slow, ongoing and expensive ad-hoc integrations that offer low quality solutions to critical consumption and production challenges

Lack of access to critical backend enterprise data crucial to mobile and cloud enablement

Model A

Model B


Recommended Model of Convergence: “C”

Convergence Model “C” unifies service consumption and production. Each area coevolves over time to bring the strengths of each to the enterprise.


The Unified SOA & API Platform

Analytics

Developer Engagement

Gateway Services

Service Integration

Lifecycle Management


SOA & API Convergence Using DataPower

SOA Software brings a fully unified API and SOA management solution to DataPower• Lifecycle Manager brings full service lifecycle

management• Community Manager brings a feature packed

developer portal and API management solution• Policy Manager for DataPower brings service

deployment and runtime automation to your existing DataPower environment across all API and SOA use cases

IBM DataPower brings a powerful API and SOA gateway• For both API and SOA use cases• To leverage the entire IBM enterprise platform• Using appliance features you already use today


SOA & API Convergence Using DataPower


DEMO


Contact Us

[email protected]/ibm


Questions?

realizing soa and api convergence

Software

soa software api

datapower soa software

soa api convergence

soa platform

soa solutions

soa gateway

soa converging

soa convergence api