Likelihood to Recommend Oracle API Manager is well suited in a business or company that make use of Apis to facilitate access of backend services and data sources by the staff or customers or both. It is also imported in situations where all actions in a system need to be attributed to specific users.
Read full review It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?
Read full review Pros API Manager allows for REST and SOAP API's to be easily created and tracked API Manager allows for only certain people/applications to use the API (does this thru a subscriber service it provides) It also publishes the API's it is tracking so developers can easily know what interfaces already exist. The monitoring ability is a nice feature. The admin person can easily see how and where the APIs are currently being used Read full review Authentication based on OAuth 2.0 and HTTP Basic Authentication. Rate Limiting applied at different levels like Subscriber, API, Resource and Backend. Monitoring by exporting the metrics in Prometheus and traces in Jaeger. Mediation to perform transformation, orchestration etc. Read full review Cons Absence of Role-Based Access. A finer grain control on what type of users can call certain API Endpoints is needed. Performance with third-party databases isn't as fast as using Oracle Database. Long learning curve. Although Oracle API Manager provides performance and a vast deal of features, a certain level of expertise is required to effectively make use of them. Read full review Better QA testing prior to releases rollout Better support needed Read full review Alternatives Considered Oracle API Manager is much easier to learn and understand then IBM Data Power Gateway and
IBM API Connect . We selected Oracle API Manager in our company because to have a good intuitive interface with drag and drop features and because beginners and easily get up to speed to use this tool.
Read full review Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.
Read full review Return on Investment Oracle API Manager supports both REST & SOAP API's. Secure and attributable connection to back-end services and data sources. In addition to creating API's for querying data, you can also create API endpoints that can manipulate the data in the back-end databases. Although Oracle API Manager provides performance and a vast deal of features, to start with it is really important you train your people working on development, deployment and administrators to effectively use Oracle API Manager. Read full review We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service. Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer. Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there. Read full review ScreenShots