7 Habits of Effective API and Service Management
 

Like this? Share it with your network

Share

7 Habits of Effective API and Service Management

on

  • 880 views

Resources: ...

Resources:
Watch Full Webinar Here: https://www.mulesoft.com/webinars/api/seven-habits-effective-service-api-management
Discover Our Anypoint Platform for APIs: https://www.mulesoft.com/platform/api
Read more about API Management Best Practices: https://www.mulesoft.com/lp/ebook/api/effective-service-api-management

In the new enterprise, the number of services and APIs are growing at a rapid pace. In this webinar, API strategists, architects, and developers will learn how to develop an API strategy and create highly effective APIs by leveraging existing services.

Reza Shafii, Director of Product Management at MuleSoft, discusses what is SOA, how service oriented architecture differs from APIs, best practices for API management, and enterprise API needs. You will learn:
1. How to transition from service oriented architecture in the API economy
2. How to develop an API strategy
3. Keys elements of an effective API Management solution
4. Strategies to overcome service and API security and identity challenges
5. Why integration platforms help manage APIs

Statistics

Views

Total Views
880
Views on SlideShare
820
Embed Views
60

Actions

Likes
4
Downloads
32
Comments
0

3 Embeds 60

https://twitter.com 38
https://www.linkedin.com 18
http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

7 Habits of Effective API and Service Management Presentation Transcript

  • 1. 7 HABITS OF EFFECTIVE API AND SERVICE MANAGEMENT Presented by: Reza Shafii, Senior Director of Product Management, MuleSoft
  • 2. AGENDA SOA and API Management1 ! 2 ! 3 ! 4 ! 5 ! 6 API Driving Forces Enterprise API Needs Best Practices of API Management Demo of MuleSoft Service and API Anatomy
  • 3. SOA and API Management
  • 4. What is SOA? ! • SOA initiative started in mid-late 2000s ! • SOA is now replaced by API Management ! • Technical principles behind SOA and API are really the same DEFINITION ! SOA or Service Oriented Architecture is software architecture based on the creation of a repository of standardized and reusable services which can be composed into an aggregate service to automate a business process. This is known as service-orientation.
  • 5. SOA and API Are Complementary Topics ! ✔ Services ✔ Governance ✔ Reuse ✔ Abstraction ✔ APIs ✔ Management ✔ Reuse ✔ Abstraction SOA API
  • 6. WHAT'S THE DIFFERENCE?
  • 7. ENTER API MAN An Improved ROI model
  • 8. API Services and APIs Reuse Agility Services Agility Reuse Services and APIs Agility Reuse … SOA vs. API API Man A Waterfall Model Agile, Iterative Approach The Difference is in Size and ROI
  • 9. API SOA vs. API ! ! SOA initiatives are monolithic, top-down projects that don't start with ROI in mind ! It's better to think ROI-first. Create a well-defined interface around a service that needs to be reused or exposed right from the start.
  • 10. API Services and APIs Reuse Agility Services Agility Reuse Services and APIs Agility Reuse … SOA vs. API API Man A Waterfall Model Agile, Iterative Approach See the difference?
  • 11. Let's Take A Step Back: ! Looking at the service and API anatomy
  • 12. Consider a Physical World Example First, PG&E provides a service. Electricity. 1 SERVICE SERVICE
  • 13. Consider a Physical World Example This service is accessible through electrical sockets. Each socket has a certain shape or form. That is analogous to the interface or API delivered to each housing and corporate endpoint. 2 API SERVICEAPI
  • 14. Consider a Physical World Example Consumers of this API is anyone that consumes electricity. Consumers do care about the form. They don't care about the implementation, such as if PG&E uses wind energy or coal energy. 3 CONSUMER SERVICEAPICONSUMER IMPLEMENTATION
  • 15. Consider a Physical World Example This is a layered model. For instance, laptops can be using that API to build its own service like a USB socket. This is then accessed by an iPhone. 4 LAYERED MODEL SERVICEAPICONSUMER IMPLEMENTATIONAPICONSUMER
  • 16. Now, a Software World Example Let's use as an example GoogleMaps 1 SERVICE SERVICE
  • 17. Now, a Software World Example GoogleMaps is exposed as a REST API and SOAP web services API (analogous to our sockets). 2 API SERVICEAPI SOAP REST
  • 18. Now, a Software World Example There are many consumers. Examples are these two: Trulia and Tripit. For instance, Tripit needs mapping service to show where a hotel is. Both do care about the API, but don't care about actual implementation. 3 CONSUMER SERVICEAPICONSUMER IMPLEMENTATION
  • 19. Now, a Software World Example This is layered, too. Trulia and Tripit exposes their own APIs, which can use ten be used to build on apps that are accessed by another set of consumers. Examples are below. 4 LAYERED MODEL APICONSUMER SERVICEAPICONSUMER IMPLEMENTATION
  • 20. Service and API anatomy SOAP REST APICONSUMER SERVICEAPICONSUMER IMPLEMENTATION
  • 21. API Driving Forces Why, as an enterprise, should you look for API initiatives and actually implement them?
  • 22. APIs Driving Forces
  • 23. To expose business logic as an API instead of a web app or mobile app. APIs Driving Forces 1 BUSINESS AGILITY Concept that businesses and enterprises can look at new sources of revenue by creating API products. Ex. Amazon Web Services 2 API ECONOMY The world is becoming a set of interconnected devices, ranging from mobile devices to car parts or light bulbs. All have APIs and all can talk to each other. 3 INTERNET OF THINGS
  • 24. When you think API, think first REST and REST API. This is the main approach for best way to expose application programming interfaces REMEMBER!
  • 25. Enterprise API Needs
  • 26. 3 Main Categories 1 DESIGN AND DEVELOP APIS 2 RUN APIs 3 MANAGE AND SOCIALIZE APIS Consistent to develop in agile fashion Solid enterprise-grade run time Apply security and throttling tools and promote them so initial API strategy is successful
  • 27. Design and implement APIs Business Owner Architect API Developer API Specification API Implementation Development Tool 1
  • 28. Best Practices of API Management
  • 29. Best Practices of API Management 1 DESIGN AND DEVELOP APIS 2 RUN APIs 3 MANAGE AND SOCIALIZE APIS HABIT #1: Apply an API-First design approach HABIT #2: Choose a solid API runtime HABIT #3: Create A Central Service Repository HABIT #4: Manage Services Through Versions, Policies and Contracts HABIT #5: Promote and socialize your API HABIT #6: Monitor and Assess API usage HABIT #7: Refactor API to improve consumer experience & productivity
  • 30. Business Owner Architect API Developer API Specification API Implementation Development Tool ! THE PROCESS ! 1. Business Owner identifies need for API 2. Works with Architect to design API. This creates the API specification 3. The API specification is communicated by Architect to API Developer, who implements API through development tools Design and implement APIs1
  • 31. Habit #1: Apply an API-First design approach Databases On-Prem Apps SaaS / PaaS Custom Apps API Specification API Implementation Create the interface, then implement it.
  • 32. • Open source • Pattern based • API-first design • API implemented on Mule • Maven plugins for: - Project creation - API mocks creation - Automated API testing • API console • Mule Studio support About MuleSoft's APIkit APIKit
  • 33. API Dev/Ops API Implementation API Runtime THE PROCESS Run APIs2
  • 34. Habit #2: Choose a solid API runtime
  • 35. Choose a solid API runtime Be able to run API applications in the cloud and on-premise 1 HYBRID SUPPORT If your API is successful, it will be used by many customers. 2 SCALABLE AND RELIABLE Runtime provides you with strong orchestration capabilities 3 STRONG MEDIATION
  • 36. • On-premise and Cloud support - Full portability • Enterprise-grade Runtime - Proven and mature • Strong mediation capabilities - To translate between API layer and backend Mule and CloudHub as API runtime Used by a huge number of Fortune 500 companies
  • 37. Business Owner Architect Service Repository Policy and Contract Management AnalyticsCentral Developer Portal App Developers Manage and Socialize APIs3
  • 38. Manage and Socialize APIs3 Remember to go over: ! • Security and throttling policies • Carefully managing consumers of those APIs • Establishing a developer portal that is really easy for a developer to come in and use the API • Reviewing analytics metrics Service Repository Policy and Contract Management AnalyticsCentral Developer Portal
  • 39. • Single source of truth catalogue ! • Categorization and search ! • Web based access Habit #3: Create A Central Service Repository
  • 40. • Tracking service versions and consumers ! • Managing their contracts and SLAs ! • Dynamic policies Habit #4: Manage Services Through Versions, Policies and Contracts
  • 41. • Create easy-to access and central API developer portal ! • Provide and encourage content that simplify API consumption Habit #5: Promote and socialize your API
  • 42. • Usage metrics - Overall and per consumer ! • Operational metrics Habit #6: Monitor and Assess API usage
  • 43. Habit #7: Refactor API to improve consumer experience & productivity APIs need continuous improvement. ! Go through the first six habits repeatedly to hit those ROIs that you defined at the beginning of your API strategy. DON'T FORGET!
  • 44. HOW DOES MULESOFT HELP?
  • 45. Demo ! End-to-End API Management with the Anypoint Platform
  • 46. ! • Service/API implementation consists of Mule flow ! • Anypoint Service Registry enables governance Demo architecture and topology - Part I Back-­‐end  Service Service  Implementation   (Mule  ESB) Service P P Anypoint   Service  Registry Apply   Policies Consumer     Requests
  • 47. API  Gateway   (CloudHub) • Mule as an API gateway to provide • API Abstraction • Security and throttling policies • Routing and orchestration ! • Support for Mule and non- Mule services ! • Anypoint Service Registry enables management ! • APIhub used to expose API for in developer portal Demo architecture and topology - Part II Backend  Service Back-­‐end  Service API  Gateway   (Mule  ESB) APIkit  API P P Anypoint   Service   Registry Backend  Service Backend  Services Apply   Policies Service  Client Meta-­‐data  based   dynamic  lookup
  • 48. Addressing end-to-end Enterprise API needs with the Anypoint Platform Find out More Here --> https://www.mulesoft.com/platform/api
  • 49. SUMMARY 1 ! 2 ! 3 ! 4 ! 5 ! 6 ! 7 Apply an API-First design approach ! Choose a solid API runtime ! Create a central Service Repository ! Manage services through versions, policies and contracts ! Promote and socialize your API ! Monitor and assess API usage ! Refactor API to improve consumer experience & productivity
  • 50. Thanks for Your Attention! Read Reza's Blog Posts: http://blogs.mulesoft.org/author/reza-shafii/ https://www.linkedin.com/in/rezashafii reza.shafii@mulesoft.com Follow Us! #MuleSoftWebinar Watch Full Webinar: https://www.mulesoft.com/webinars/api/seven-habits-effective-service-api-management Anypoint Platform for API: https://www.mulesoft.com/platform/api Ebook on API Management Best Practices: https://www.mulesoft.com/lp/ebook/api/effective-service-api-management