Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

API Governance in the Enterprise

Consultant Robert Broeckelmann shares his experience of implementing API management in a large enterprise and will share how to:

- define API governance
- explore the goals, requirements, implementation of API governance
- look at lessons learned from implementing one enterprise customer's API governance process

  • Be the first to comment

API Governance in the Enterprise

  1. 1. ©2016 Apigee Corp. All Rights Reserved. API Governance in the Enterprise Robert Broeckelmann, Levvel Dino Chiesa, Apigee
  2. 2. ©2016 Apigee Corp. All Rights Reserved. Slideshare Apigee Community YouTube
  3. 3. Presentation Title API Governance In The Enterprise Robert C. Broeckelmann Jr.
  4. 4. DISCLAIMERS • What we present here is one of numerous possible ways to use Apigee technology. Your situation and requirements will probably differ. • As always, test things in a non-production environment prior to using anything in production. • We are not responsible for spontaneous combustion of the known universe or any other undesirable outcomes associated with using what is discussed here. 3
  5. 5. AGENDA • What is API Management? • API Management--The Full Stack • API Management Solution Architecture • What Is API Governance? • One Organization’s Requirements • API Lifecycle Management • API Governance Ties Into... • Lessons Learned • Questions 4
  6. 6. WHAT IS API MANAGEMENT? Allows an organized approach to using APIs to open up an organization or system’s data so that it can be utilized by other parts of the organization or third-parties in new and useful ways. 5
  7. 7. WHAT IS API MANAGEMENT? From a business perspective, API Management is a revolution; from a technical perspective, it is an evolution of the earlier Service Oriented Architecture (SOA) paradigm. 6
  8. 8. WHAT IS API MANAGEMENT? Spans B2E, B2C, B2B User Spaces Spans Mobile, Integration, Identity, Security concerns. 7
  9. 9. WHAT IS API MANAGEMENT? • The process of publishing, promoting, and overseeing APIs in a secure, scalable environment • Ensuring that developers and partners are productive • Managing, securing, and mediating your API traffic • Allowing an organization to grow their API program to meet increasing demands • Enabling the monetization of APIs • The intersection of technology, business, organization, and integration concerns 8
  10. 10. THE API MANAGEMENT ”FULL STACK” 9 Data Modeling Interface Modeling API Management Solution Management Portal Developer Portal API Gateway Registry & Repository Identity Stack Application Infrastructure Monitoring User Repositor y Federatio n User Provisioni ng Applicatio n Firewall Reverse Proxy DevOps Logging
  12. 12. WHAT IS API GOVERNANCE? API Governance is also part of API Management… … probably the most important part. 11
  13. 13. WHAT IS API GOVERNANCE? Governance is not a bad thing; though, your experiences with it would, probably, make you disagree. In fact, for anything to be truly adopted by the enterprise, it must have adequate and functional governance. The trick is to strike the right balance. Self-service and automation is the key to making the governance process(es) workable. 12
  14. 14. WHAT IS API GOVERNANCE? Allows for a policy driven approach (vs. ad hoc) to enforcement; not just runtime, but throughout the design and development process •single point to manage policies and enforcement. 13
  15. 15. WHAT IS API GOVERNANCE? API governance includes: ●tracking what (API) is deployed where (environment) ●tracking who is calling what ●how is it (API) protected? ●defining interface standards ●gathering statistics (about API consumers, APIs, and the Developer Portal) ●API versioning ●JSON (or XML) Schema versioning ●tracking routing information ●tracking what policy should be applied to it (API) ●sun-setting (retiring a version of the API) 14
  16. 16. One Organization’s Requirements • Every organization’s governance requirements will have some unique aspects. • There will also be a large amount of overlap. • Example Requirements this organization had • Isolation between Non-Production and Production. Two Apigee organizations; (NP: 3 environments, PRD: 1 environment) • Four environments included in SDLC (Software Development Life Cycle) • Organization uses Swagger 2.0 to describe interfaces
  17. 17. One Organization’s Requirements •Requirements • 3rd Party IdP (Azure Active Directory) used • AAD acts as token generator for all actors. Apigee customized to work with AAD-produced tokens. • came from the organization's IAM and Information Security teams. • drove much complexity • Top-down development methodology utilized. • Building a program that supports the entire business. Rather than a particular line of business or development group. • Many different concerns. 16
  18. 18. API LIFECYCLE MANAGEMENT API Lifecycle Management (which tracks the interface’s life-cycle, not the implementation) is part of API Governance. The details will vary, but this basically describes the promotion process (life-cycle) of an API version from initial concept, to definition, to the lowest-level development environment, to production, and eventually to sun-setting. 17
  19. 19. API LIFECYCLE MANAGEMENT Suppose your organization has the following environments: • Unit Test Environment • Quality Assurance Environment • Load Test Environment • Production Environment Now, let’s assume that your API life-cycle captures the following additional steps: • Inception (identification of a business or technical need) • Definition (interface definition) • Development • Sun-setting (retiring a version of the API) The API Lifecycle will account for all of these states 18
  20. 20. API GOVERNANCE TIES INTO API Governance ties into: • Change Management • Asset Management • Configuration Management • Legacy SOA Governance (with the goal of eventually replacing it) • Quality Assurance • Information Security • IT Auditing Within Enterprise IT all of these things are interrelated. The processes and organization should reflect this. Yes, it sounds heavy weight. But, effective self-service and good processes makes all the difference in the world. 19
  21. 21. DEVOPS TIE-IN API Governance ties into DevOps •The Developer Portal provides a self-service platform to allow developers to  register with the system  create applications  provision credentials  subscribe to APIs  view documentation  other activities •The Developer Portal can also  increase development and decrease cycle time  decrease Mean Time To Resolution (MTTR)  enable stakeholder-level overview  ease compliance and reporting 20
  22. 22. LESSONS LEARNED Most small to medium sized organizations can probably use the Apigee developer portal and built-in processes out of the box without significant modification. • The enterprise IT organization is different. Different = messy details. • There are exceptions to every rule (including this one). • There is probably a small or medium sized organization out there that has had to deal with these issues. 21
  23. 23. LESSONS LEARNED Not all organizations are focused on opening their data up to arbitrary third parties. It may be that internal development teams and B2B Business Partner development teams are the primary focus of the API Management Developer Portal. • Not the API Management use case we often hear about, but very important for many organizations. • Anything that involves interacting with many development teams outside of your control can benefit from an API Management solution to better manage and communicate with those actors. 22
  24. 24. LESSONS LEARNED For this organization, API Governance was an evolution of SOA Governance paradigm that was already in place. • Not starting from scratch. Executive sponsorship, buy-in from business/senior management is critical. 23
  25. 25. LESSONS LEARNED Integration with a Third Party Identity Provider is likely imperative in a large organization. • Is Apigee Edge or the third-party IdP issuing tokens to API consumers? If third-party IdP, introduces much complexity to Edge. If so, applications must be registered with the third-party IdP and Apigee Edge. If the third-party IdP is issuing tokens, necessitates replicating client identifiers into Apigee Edge's IdP for Quota Enforcement and Business Analytics. 24
  26. 26. LESSONS LEARNED • The group that is supporting your Apigee Edge API Gateway may not be the same group that supports the Developer Portal infrastructure. Different skill sets. • Drupals/PHP vs. Javascript/node.js/Edge Policy • Apigee Developer Portal did not have good support for multiple endpoints for the same API. Had to import the same Swagger for each endpoint (one endpoint per environment).
  27. 27. Thank you

    Be the first to comment

    Login to see the comments

  • zheng_chao1008

    Dec. 7, 2016
  • AjayKanukuntla1

    Apr. 4, 2017
  • Conore7

    Apr. 6, 2017
  • PavelSheynkman

    May. 6, 2017
  • AnupamaSatyavolu

    Jun. 21, 2017
  • FabianaDeBritoValent

    Jun. 22, 2017
  • LeonardoBertolini2

    Aug. 30, 2017
  • DisasterNet

    Jan. 20, 2018
  • MarkJohnson89

    Apr. 20, 2018
  • GangaAloori

    Jun. 11, 2018
  • Gudimetla

    Aug. 29, 2018
  • kanukollunaren

    Dec. 8, 2018
  • ChaithanyaPadi1

    May. 21, 2019
  • BhaskarBabu3

    Jun. 19, 2019
  • JorgeBlomDahlOliver

    Sep. 10, 2019

    Sep. 17, 2019
  • rguo2016

    Apr. 13, 2020

Consultant Robert Broeckelmann shares his experience of implementing API management in a large enterprise and will share how to: - define API governance - explore the goals, requirements, implementation of API governance - look at lessons learned from implementing one enterprise customer's API governance process


Total views


On Slideshare


From embeds


Number of embeds