Think Small: API Architecture For The Enterprise

Transcription

1 Think Small: API Architecture For The Enterprise Ed Julson - TIBCO Product Marketing Raji Narayanan - TIBCO Product Management October 25, 2017

2 DISCLAIMER 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. 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 could experience factors that could cause actual results or financial performance to differ materially from those contained in any forward-looking statement made in connection with this presentation. TIBCO does not undertake to update any forward-looking statements that may be made from time to time or on its behalf. 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 the information 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.

3 Digital Transformation is Driving API Evolution New Biz Models Smart Analytics New Channels Emerging API Needs: Microservices Event-Driven IoT Devices Mobile Serverless/FaaS Edge Machine Learning Conversational Experiences Partner Expansion Chatbots Sensors Streaming Realtime Data This document (including, without limitation, any product roadmap or statement of direction Copyright data) illustrates the planned testing, TIBCO release Software and availability Inc. dates for TIBCO products and services. It is for informational purposes only

4 Gateways Need to Evolve Too Existing gateways not built for: Microservices Developer Tooling Microservices Choreography Complex Message Patterns True micro Footprint Service Meshes APIs Op1 Op2 Op3 Op4 Op5

5 So, What Changes? By 2020, 50% of organizations managing APIs will Incorporate event-driven APIs into their architecture * RESTful APIs Client Driven Inherently Synchronous Must be Available One to One Service Mediation Event-Driven APIs Client or Server Driven Inherently Asynchronous Can be Buffered Can be Many to Many Event Mediation * Source: Gartner; The Impact of Event-Driven IT on API Management (April 2017) 5

6 Rest API Good: Request/Response API Today Monolithic Application Request/response pattern; fixed inputs & outputs Streaming data or server-side pushes not supported Works best with well defined, repeatable use cases Shopping Cart Shopper Tracking Customer Smartphone Request API Gateway Shipping Response Product Catalog Pricing Payment Pricing

7 Better: Microservices Request/Response API Monolithic Application Fine-grained APIs improve scalability & response Supports serverless and FaaS consumption Isolated services easier & faster to change Request/response pattern limits API use cases Rest API Rest API Shopping Cart Shopper Tracking Customer Smartphone Request API Gateway Rest API Shipping Response Rest API Product Catalog Rest API Pricing Rest API Payment Pricing 7

8 Microservices: In Active Use Today Source: Forrester Research; Microservices and External APIs Underpin Digital Business (Oct 17, 2017) Among development managers who said that changing their business model was likely to be a critical or high business priority, 62% already have microservices or plan to have them by early among those having implemented REST APIs, only 25% say that all or nearly all of them are designed as entirely CRUD APIs, which shows that many organizations feel the need to go against the religion....among development managers with internal APIs, 23% said they have important use cases, where one call to an API must update multiple applications. 8

9 Best: Event-Driven Microservices & APIs Shopper Tracking Micro Event Gateway Handler 2 Start Tracking (Pub/Sub) 5 Price Query (Request/Reply) Pricing Micro Event Gateway Handler Customer Smartphone 1 Add to cart (Pub/Sub) Shopping Cart 4 Get Pricing (Request/Reply) Product Catalog Shipping 7 Execute Pmt (Pub/Sub) Payment Micro Event Gateway Handler 3 Check Promos (Request/Reply) Micro Event Gateway Handler 6 Ship Quote (Pub/Sub) Micro Event Gateway Handler Micro Event Gateway Handler Promotions Micro Event Gateway Handler Event based, behavior is flexible Mixed MEPs supported Events can come from anywhere Best approach for realtime applications

10 The Evented Microservices Developer Gap Tooling Event handlers Loosely coupled events Pub/sub & other MEPs Codeless tooling Lightweight Runtime Minimal overhead Distributed & federated Easy to modify Multi-Architecture Support for Edge Computing Serverless & FaaS Service mesh interop

11 Current Marketplace Options API Gateways Traditional API Gateways Commercial Products Sophisticated Security & API Mgt Policies Service Meshes Microservices-Oriented Open Source Layer for Service Interaction, Reliability & Monitoring Microgateways Lighter Weight Than API Gateways Open Source Simple Proxy for Request/Response However Lack Eventing Capabilities Are Heavyweight However Lack Eventing Capabilities Lack API-Led Development However Lack Eventing Capabilities Light on Operational Functions 11

12 Project Mashling The Only Open Source Event-driven Microgateway Ultralight & Embeddable Event-driven by design Complements service meshes Publish APIs to Mashery

13 and its contents are subject to change without notice. Copyright Copyright TIBCO Software Inc. All rights reserved. TIBCO Proprietary Information. TIBCO How Project Mashling Adds Value Speeds Up Microservices Development Mashling accelerates developer productivity for microservices with visual tooling and sharable, flow-based recipes Foundation for Evented APIs and Applications Composable, event-driven microservices and APIs that interoperate with service mesh open source, can be developed using the Mashling framework Extreme Flexibility in Gateway Deployment Small 5MB footprint runs anywhere and can be embedded in edge devices or deployed as a federated microgateway co-located with applications

14 Embracing Open Source, Sharing Our Innovations Leverage open source projects or partner with TIBCO for commercial enterprise-ready versions, with support services Project Flogo Ultralight Edge Microservices Framework Project Mashling Open Source Event- Driven Microgateway

15 Open Source, TIBCO s Foundation For Innovation TIBCO Mashery Commercial support with Mashery Local Available Q Open Source Project Flogo Develop Ultralight Microservices Developer-Centric Focus GoLang based & visual flow designer Edge Device & IoT Optimized FaaS & Serverless Support 100% OSS + Community Support Open Source Project Mashling Event-Driven Microgateway Developer-Centric Focus Available Now Re-usable Recipes Service Mesh Compatibility 100% OSS + Community Support This document (including, without limitation, any product roadmap or statement of direction Copyright data) illustrates the planned testing, TIBCO release Software and availability Inc. dates for TIBCO products and services. It is for informational purposes only

16 Sample Customer Scenarios Telco Example Retailer Example Manufacturing Example Existing TIBCO customer Large scale BW Engines Multiple legacy gateways New landscape = BWCE + SpringBoot + Pivotal CF Key requirement is a developer friendly microgateway New TIBCO customer Landscape is BW Container Edition + Flogo + Docker Key requirement is an embeddable gateway framework that works with service meshes Large OEM TIBCO customer Landscape = Thingworx + Spotfire + Custom apps Key requirement is an embeddable gateway for IOT devices and edge 16

17 Federated Gateways and Microservices Kafka / MQTT TIBCO Messaging TIBCO Messaging Serverless / FaaS Docker Swarm Bounded Microservices Kubernetes Bounded Microservices SOA/ESB Domain Svc A F(x) F(y) Svc B Svc C B Federated Gateway Architecture Embedded Gateway Cloud Gateway On-Prem Gateway Developer Portal API Creation API Packager API Policies Analytics 17

18 User Persona - Aaron Ramos, the Microservices Dev Developer building microservices Preferred toolchain : Node.js, Go, Kafka, Docker, Envoy Typically part of a 2-pizza team with end-to-end DevOps responsibility for the microservice Interested in event-driven patterns NOT your typical API Product Manager persona nor an API Gateway Operator

19 Aaron s Journey & Workflows - Summary 1-click CI Deploys Browse recipes on GitHub Search community of recipes Import into IDE Publish API endpoint to Mashery Browse recipes on mashling.io Edit recipe on mashling.io Config to deploy in < 3 mins & < 2 clicks

20 Project Mashling Demo This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for TIBCO 20 products and services. It is for informational purposes only

21 How can I get started? to browse, download and customize microgateway recipes github.com/tibcosoftware/mashling for access to CLI, library and extensions 21

22

23 Kafka/MQTT TIBCO Messaging TIBCO Messaging Illustrative Customer Landscape - Federated Gateways & Microservices API Platform Serverless & FaaS font/ colors cleanup Dev Portal Analytics μs API Packager API Policies μs Federated API Gateway μs Svc A On Prem Cloud IoT μs Microservices Bounded Context B Kubernetes Svc B Svc C Microservices Bounded Context A Docker Swarm SOA/ESB Domain