TIBCO Mashery -ow IT Can enable enterprise API

Andy Hampshire

TIBCO Mashery Technical Evangelist

How IT can Enable the Enterprise With API’s

Webinar Recording

Today’s webinar is being recorded and a link to the recording will be emailed to all webinar registrants

Have A Question?

Submit questions using the Q&A panel on your Webinar application

Housekeeping

This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO products and services. This document is provided for informational purposes only and its contents are subject to change without notice. TIBCO makes no warranties, express or implied, in or relating to this document or any information in it, including, without limitation, that this document, or any information in it, is error-free or meets any conditions of merchantability or fitness for a particular purpose. This document may not be reproduced or transmitted in any form or by any means without our prior written permission. The material provided is for informational purposes only, and should not be relied on in making a purchasing decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. During the course of this presentation TIBCO or its representatives may make forward-looking statements regarding future events, TIBCO’s future results or our future financial performance. These statements are based on management’s current expectations. Although we believe that the expectations reflected in the forward-looking statements contained in this presentation are reasonable, these expectations or any of the forward-looking statements could prove to be incorrect and actual results or financial performance could differ materially from those stated herein. TIBCO does not undertake to update any forward-looking statement that may be made from time to time or on its behalf.

DISCLAIMER

© Copyright 2000-2017 TIBCO Software Inc.

The following information is confidential information of TIBCO Software Inc. Use, duplication, transmission, or republication for any purpose without the prior written consent of TIBCO is expressly prohibited.

CONFIDENTIALITY



Agenda

Introduction

APIs By Design

API’s as a Service

Driving Innovation and Reuse

IOT and Smart Industry

Q&A


Introduction

API’s are still 2017 hottest industry subject alongside DevOps, Microservices and IOT API’s - business problem or business opportunity ? •  Even LOB Execs are talking about API’s •  Business benefits from extension of reach •  IT Benefits come from agility, but don’t pay for agility with a lack of integrity API’s Everywhere •  Inside the enterprise •  On the cloud


IT is seen as the Business preventer, not the enabler

•  IT has to protect the resources •  Be Agile but controlled •  Break and fix fast might work •  Don’t risk core Integrity


API Design

With API First design API’s will be everywhere API’s no longer the By-product Of An App …. Now the Product Focus •  Functionality & requirements •  Usage Patterns •  Deployment models


API Right Sizing

Getting the granularity right Big is Bad, or is it ?

•  Just think of that all important core bank app, running on antiquated hardware, with few ways to get at the data.

•  The API from hell, everyone has one … WSDL based service that does everything to every business object ?

Small is better… but is it always ? •  Few situations where agile isn’t best •  API Rightsizing through Service Composition


API Classification

API Classes ? Types ? Sets ? Number of ways the problem can be expressed

Experience Application

Core


API Classification

Experience Layer

Application Application Application

Core Core Core Core Core

Corp

Core IT

LoB IT

App Devs


API Right Sizing

Usage not misuse

API

Client Client Client Client Client Client Client Client Client Client Client


API Right Sizing

Usage not misuse

API

Client Client Client Client Client Client Client Client Client Client Client

API Management

API V2

API DR


API Orchestration

Interlinked API Network


API Orchestration

Orchestration API’s


API Orchestration

Mediation API’s


Focus on Functionality

Developers build business logic

Shouldn’t need to worry about o  Deployment Model o  Security Policies o  Handling SLA’s


API design

Rule 1 – Keep it common Follow a design pattern and stick to it For example: http://www.narwhl.com

Rule 2 – Not all API users are as clever as you

Full Level 3 HATEOAS is cool but is it required ? Just Keep it simple

Rule 3 – Careful what you change

Follow best practice for “breaking changes”


API Deployment

Java J2EE NodeJs TIBCO

BW

API Management


API’s as a Service

API’s will be everywhere

Management layer in the cloud to handle all cloud requests Look for Worldwide traffic management to seamlessly route workloads Reduced costs and faster to deploy

Offload skills requirement for IT group Use Hybrid solution for Internal use and specific external use cases


Driving Innovation

Creating API’s that will drive innovative use is still an art, designing the API’s that will be most effective for the target user community needs to become a science.

IT needs to shift roles if companies are going to stay competitive and innovative. They need to become more efficient and expose data and services in a consistent manner that provides the same level of governance with far less delay. They need to stop being the gatekeepers and become, instead, a service organization - they need to help their developers, analysts and business folks get their jobs done quickly. APIs and good API management help because all data is presented through a single layer that Ops can maintain through a simple admin interface, no matter where those services live. Adding self service makes things move even more smoothly. This lets ops focus on maintaining their systems and shifts a lot of the administrative weirdness to an automated, yet secure, system.


Driving reuse

Build it and they won’t come Portal is required but not enough on it own Actively manage and promote by an API Manager Package up API’s into useful groups Document, document and then document some more Use analytics to understand how API’s are used Solicit user feedback Just be creative !


Microservices and API’s

Lead with API First approach API’s align with deployable microservices Size is your enemy Forgiving clients are your friends New Event based paradigms ●  Event Sourcing ●  Event Streaming


Enabling IOT and Industry 4.0

IOT •  Mainly going to be streaming API’s

(sensor data) •  Small payloads

Smart Manufacturing •  As companies buy into the concept of Mass Customization,rather than mass

production, API’s become key •  Consumers will innovation … Retail app that allows for ordering of an outfit,

colour coordinated, and tailored to user specifics across suppliers.

Audience Q&A

Submit your questions using the Q&A panel on your Webinar application.

Next Steps

•  Join TIBCO Mashery 30-day Free Trial

•  https://www.mashery.com/trial-signup

•  Access a product demo from the mashery.com website

•  For Support or Sales queries, please contact us at

•  http://www.tibco.com/contact-us


Share Your Feedback!

Thank You for Joining Us!


Technology

TIBCO Mashery -ow IT Can enable enterprise API