Architecture in the API Era

(1)

Architecture in the API Era

Mark Sigda

Senior Principal Consultant, CA Technologies

May 21, 2015

ITARC

(2)

Mark Sigda

 Fort Collins, Colorado, USA

 IASA member since 2007

 CITA-F Certified

 MCAD

 MSEE

(3)

(4)

(5)

History

-1999 – Web Meets the Enterprise 2000-03 – Rise of SOA •SOAP-based Web Services •WS-* •“SOA” 2004-07 – SOA Golden Age •“ESB” •SOA Governance •SOA is state of the art

2008-11 – A New Paradigm

•Cloud & SaaS •Mobile •SOA fades

2012-14 – APIs Prevail

(6)

Web API Drivers

(7)

The

Open

Enterprise

Developer Community

Cloud Services

Partners/Divisions

Mobile Apps

(8)

The API has become the key business and technology

integration point.

(9)

(10)

The

Open

Enterprise

Developer Community

Cloud Services

Partners/Divisions

Mobile Apps

(11)

(12)

API Gateway Pattern

 Keep your APIs together

 Keep your API interface separate

 Keep your policies out of your code

– Declarative

– Centralized

(13)

API Gateway Pattern

API Gateway

Security & Identity

Traffic Management

Integration

Consumers

AJAX Web Apps

Mobile Apps

IoT Devices

APIs/Services

Back-end

REST APIs

IAM

Analytics

SOAP Services

(14)

(15)

API Management (APIM)

 Forrester – API Management

(16)

(17)

(18)

API Gateway

 Runtime network appliance

 Single entry point for APIs

 Policy:

(19)

API Portal

 Web application

 API Catalog

(20)

API Management Suite

API Gateway

…

Developers

Applications

API Developer Portal

Design Time

(21)

(22)

Role of the Architect

 Design APIs

 Document APIs

 Security & Identity

 Traffic management (SLA, tracking)

 API Infrastructure

(23)

Trends (1 of 2)

 API as a first-class product

 “API First”

 Separate Policy & Code

 API Management COTS

 Build for your client

(24)

Trends (2 of 2)

 OAuth

 Brokered identity management

 Microservices & “No ESB”

 IoT

(25)

(26)

(27)

Legal Notice

Copyright © 2014 CA. All rights reserved. Office 365 is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies. No unauthorized use, copying or distribution permitted.

THIS PRESENTATION IS FOR YOUR INFORMATIONAL PURPOSES ONLY. CA assumes no responsibility for the accuracy or completeness of the information. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING, WITHOUT

LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. In no event will CA be liable for any loss or damage, direct or indirect, in connection with this presentation, including, without limitation, lost profits, lost investment, business interruption, goodwill, or lost data, even if CA is expressly advised of the possibility of such damages.

Certain information in this presentation may outline CA’s general product direction. This presentation shall not serve to (i) affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (ii) amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion.

Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in this

presentation, CA may make such release available (i) for sale to new licensees of such product; and (ii) in the form of a regularly scheduled major product release. Such releases may be made available to current licensees of such product who are current subscribers to CA maintenance and support on a when and if-available basis.