Managing APIs with Cloud Foundry Route Services and Apigee Edge
•
6 gefällt mir•2,448 views
This document discusses API management and how route services in Cloud Foundry can be used to seamlessly integrate API management. It introduces API management and route services, demonstrates how to bind an Apigee route service to an application, and discusses how this allows for traffic control and transformation configurations in Apigee without additional development effort. The integration of Pivotal Cloud Foundry and Apigee Edge is provided as an example of how route services can integrate API management capabilities.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (19)
Ähnlich wie Managing APIs with Cloud Foundry Route Services and Apigee Edge
Ähnlich wie Managing APIs with Cloud Foundry Route Services and Apigee Edge (20)
Mehr von Kazuchika Sekiya
Mehr von Kazuchika Sekiya (17)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Managing APIs with Cloud Foundry Route Services and Apigee Edge
- 1. ©2015 Apigee Corp. All Rights Reserved. Routeサービスを使ったCloud FoundryアプリのAPI管理 Kazuchika Sekiya (Apigee) Gwenn Etourneau (Pivotal)
- 2. ©2015 Apigee Corp. All Rights Reserved. 自己紹介 2 買収 買収転職 関谷 和愛 Solution Architect, Apigee https://about.me/kazuchika #java #groovy #api
- 3. ©2015 Apigee Corp. All Rights Reserved. What is API? Why APIs? 3
- 4. ©2015 Apigee Corp. All Rights Reserved. What is API? 4
- 5. ©2015 Apigee Corp. All Rights Reserved. Why APIs? Open APIとAPIエコノミー 5
- 6. ©2015 Apigee Corp. All Rights Reserved. Why APIs? Microservices 6 MONOLITH MICROSERVICES SHOPPING CART CATALOG CUSTOMER RECOMMEND REVIES APIs
- 7. ©2015 Apigee Corp. All Rights Reserved. What is API Management ? 7
- 8. ©2015 Apigee Corp. All Rights Reserved. What is API Management? 8
- 9. ©2015 Apigee Corp. All Rights Reserved. Apigee: The API Company 9 API管理サービスのパイオニア＆リーダー
- 10. What are CF Route Services? A new kind of marketplace service that can be injected in the application request path 10
- 11. Why Route Services Compliance, Security, Audit • Enable developers to automatically insert services into the request path for their applications and configure them for their specific needs • A new class of marketplace service (User-provided also supported). • Increasing developer velocity through automated, self- service integrations 11
- 12. What is Routing Compliance, Security, Audit • Routing in Cloud Foundry is the process by which requests to applications are forwarded to their intended destination • A dynamic routing tier is necessary because Cloud Foundry may move application instances between hosts for high availability • Developers manage the URLs their applications receive requests for • Requests to Cloud Foundry system components are managed this way, too 12
- 13. How are PCF Route Services used? Ensure Performance, Reliability Compliance, Security, Audit Real Time Analytics, Metering Compliance, Security, Audit 13
- 15. Service broker Compliance, Security, Audit • Service Brokers provide an interface / API for native and external 3rd party services. • Some example like Database, Route Service, Persistent Storage, Container networking and so on. • Limit is your imagination… 15
- 16. Operators 1. Given a compatible service, simply register the service broker cf create-service-broker NAME USERNAME PASSWORD URL 2. Grant or revoke access to service plans per CF organization cf enable-service-access SERVICE -p PLAN -o ORG 3. Log and audit use of services cf curl /v2/events?q=type:audit.se rvice_instance.create 16
- 17. Developers 1.) Discover service in marketplace cf marketplace 2.) Create a CUPS or a Marketplace service cf create-user-provided- service SERVICE_INSTANCE - r ROUTE_SERVICE_URL or cf create-service SERVICE PLAN SERVICE_INSTANCE 3.) Bind Routing Service to the Route cf bind-route-service DOMAIN --hostname HOST SERVICE_INSTANCE 17
- 18. Simple Route Services Gorouter App Service Broker Client Gorouter App Servic e Broker Route Services Dynamic Client How Route Services work 18
- 19. ©2015 Apigee Corp. All Rights Reserved. デモ 19
- 20. ©2015 Apigee Corp. All Rights Reserved. Routeサービスを使ったシームレスなAPI管理の統合 20 App Clients or Partner Apps CF Router YOUR APP Apigee Service Broker Apigee Management API API Proxy (Route Service) 1 Install Apigee Tile from CF marketplace & create Apigee Edge service 2 Bind route service for your app to Apigee 3 Apigee automatically creates API proxy, policies are applied and APIs can be published to Developer portal 4 All requests automatically routed to Apigee for security, analytics and traffic management
- 21. ©2015 Apigee Corp. All Rights Reserved. デモ • APIアプリをプッシュ • ルートサービスを生成してアプリにバインド • API管理側でトラフィック制御や変換などの設定を試す 21
- 22. ©2015 Apigee Corp. All Rights Reserved. まとめ • Why APIs? – APIエコノミー、Microservices • API管理はAPIの効率的な開発・運用を強力にサポート – 認証・認可、トラフィック管理、アナリティクス – コア機能の開発に集中できる • CFではRouteサービスによりシームレスにAPI管理を統合可能 – Pivotal Cloud FoundryとApigee Edgeの統合例 22
Hinweis der Redaktion
- What business needs does route services address for our customers? Time to market for differentiated capabilities in the realms of… Real Time Analytics: Report on and analyze real time behavior, events based on network – level information Compliance, Security Performance, Reliability How can customers get various route services, now and in the future? From Pivotal From Partners From customers making their own
- What business needs does route services address for our customers? Time to market for differentiated capabilities in the realms of… Real Time Analytics: Report on and analyze real time behavior, events based on network – level information Compliance, Security Performance, Reliability How can customers get various route services, now and in the future? From Pivotal From Partners From customers making their own
- What business needs does route services address for our customers? Time to market for differentiated capabilities in the realms of… Real Time Analytics: Report on and analyze real time behavior, events based on network – level information Compliance, Security Performance, Reliability How can customers get various route services, now and in the future? From Pivotal From Partners From customers making their own
- Operators Responding to individual developer needs is time consuming Responding promptly is difficult, and requests may not be aligned with policies We want to provide operators with solution they can put in place once, configured with policy, and enable developers to pick and choose, self-service Developers Features like authorization and rate limiting are common requirements in application development and operation Currently developers must either build these features into their applications or coordinate with IT to provide them Eliminate unnecessary development and support ticket wait-time Automated, self-service, on-demand, integrated services
- Operators Responding to individual developer needs is time consuming Responding promptly is difficult, and requests may not be aligned with policies We want to provide operators with solution they can put in place once, configured with policy, and enable developers to pick and choose, self-service Developers Features like authorization and rate limiting are common requirements in application development and operation Currently developers must either build these features into their applications or coordinate with IT to provide them Eliminate unnecessary development and support ticket wait-time Automated, self-service, on-demand, integrated services
- Operators Responding to individual developer needs is time consuming Responding promptly is difficult, and requests may not be aligned with policies We want to provide operators with solution they can put in place once, configured with policy, and enable developers to pick and choose, self-service Developers Features like authorization and rate limiting are common requirements in application development and operation Currently developers must either build these features into their applications or coordinate with IT to provide them Eliminate unnecessary development and support ticket wait-time Automated, self-service, on-demand, integrated services
- (LEFT) Simplest model for RS integration in which all HTTP requests to CF are intercepted. RS does some transformation on the Request and forwards it to the Gorouter. Broker enables developer configuration. (RIGHT) More dynamic integration enables only requests for a particular route to be proxied to the RS, before being returned to Gorouter. Enables dynamic integration of services operated by 3rd parties. Broker enables developer configuration (and/or provisioning). When Gorouter receives the request from the route service, it uses an encrypted header to determine the request has already been sent to the RS, and forwards the request to the app.