Mule api and service management
Download as PPT, PDF0 likes435 views
This document discusses API management and its differences from SOA. It notes that API management uses a "bottom-up" approach of wrapping services with accessible interfaces, shielding consumers from underlying technologies. This delivers on promises of SOA like accelerated development and improved effectiveness. The document provides an analogy comparing an API to an electrical socket, acting as an interface between services and consumers. It outlines benefits of APIs like enabling business agility and facilitating an emerging API economy.
Mule api and service management
- 1. Mule-API and Service Management
- 2. 2 Mule-API and Service Management API management is essentially the next generation of SOA. But how will API management avoid the well-known pitfalls that derailed so many SOA initiatives? While API management shares many commonalities with SOA, there are two key differences. First, rather than a top-down, rip-and-replace approach, API management uses a “bottom-up,” wrap-and-renew approach. APIs essentially breathe new life into services by layering accessible and developer-friendly interfaces on top of them, effectively shielding consumers from the underlying technology. Secondly, API initiatives are all about ROI.
- 3. 3 This approach delivers on the initial promises of SOA and more: • Accelerated application development • Reduced risk of failure • Improved developer effectiveness
- 4. 4 Providing an External HTTP or HTTPS Port API and Service are interchangeable terms, while others think they’re at opposite ends of the spectrum. Before moving on, it’s important to establish a common Programming Interface provides a way for developers to interact with and consume a service.
- 5. 5 An analogy is useful in illustrating what this really means, so let’s consider a service that all of us consume every day - electricity. Electricity is delivered to consumers by a utility company. The utility company provides a service (electricity) to consumers that is accessible through electrical sockets. These sockets vary from one country to another, limiting access to only those consumers with the correct plugs for that socket. The plugs are essentially consumers, only able to make use of the service if they have the appropriate authorization. In this case, the API is the socket itself. APIs are gateways between services and consumers, providing consumers access to services through various interfaces depending on their credentials. In addition, consumers can utilize the services they receive and implement them in their own way. Consider a laptop, which consumes electricity through a socket. Through its own “API,” a USB socket, it can provide that same electricity service to charge other devices.
- 6. 6 Organizations are beginning to understand the importance of APIs and the value they deliver to business. But what exactly is causing all the fuss? Business agility: Much more effective than creating business logic and exposing it as a website is creating business logic and exposing it as an API. With APIs, it doesn’t matter how the logic is used; clients and consumers can consume the API and expose it to their liking, delivering
- 7. 7 API economy: Businesses are developing “API products” as new sources of revenue. Expedia generates over $2 billion annually through the data made available through their API. Salesforce generates 75% of their revenue through API activity. The API economy is here and growing fast. Internet of things: The number of things that can be connected is growing fast; everything from your coffee pot to your thermostat to your car can now
- 8. 8 SOA, and the reasons behind their growing importance in the enterprise, it’s time to dig into the 7 habits that drive effective API management. If you’re starting an API initiative or wondering how to get started, following these best practices will ensure that your APIs are easy to use, fast to deploy, and deliver the business results you expect. ............................