Oracle Cloud Infrastructure (OCI) provides a comprehensive set of services to manage the lifecycle of APIs (application programming interfaces). The built-in tools let developers to collaborate on prototyping, testing, and validating APIs.
N/A
WSO2 API Manager
Score 9.4 out of 10
Enterprise companies (1,001+ employees)
WSO2 API Manager makes it possible for developers to both develop and manage APIs of different types. Unlike solutions which focus only on managing API proxies, WSO2 API Manager provides tools to develop APIs by integrating different systems as well. It supports a variety of API types from REST, SOAP, GraphQL, WebSockets, WebHooks, SSEs and gRPC APIs with specialized policies and governance for each different type. Being fully open source, its architecture and extensibility…
Oracle API Manager works well for our team since a majority of the products we use are Oracle based. Our backend jobs and servers all run with PL/SQL and Oracle databases. This makes the Oracle API Manager tool the best suited for our needs as a department. Anypoint API Manager …
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 …
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 …
Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in …
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.
WSO2 is a unique product that provides pre-integrated components like Gateway, Integrator, identity management, etc. Hence it is best suited when the requirement is not just only publish the APIs but also to secure and transform the APIs. WSO2 can be an overhead if only Gateway is required, as there are other very lightweight gateways available in the market.
Mature and Reliable. Last year, Oracle API Manager was quite buggy, and couldn't be used at production-level. Fortunately, almost all of the problems that it had previously are now patched.
Offloads Most of the Workload of Developing APIs. While defining APIs, Oracle API Manager does a great job in providing suggestions and error checks in our logic.
Supports SOAP and REST. Not only can you create APIs that can query for data, but you can also create API endpoints that can manipulate the data in your back-end databases.
I would say it would be nice if it could handle non-Oracle type API's...such as in-house developed interfaces, etc.
It would be nice if it at least could list non-Oracle type APIs so that this system became a repository for ALL of the application interfaces
Maybe it has this and I missed it, the monitoring appears to be one API at a time, would be nice to see a page that has all of the monitored APIs with some basic monitored info perhaps. It does have alerts, audit trails, and integrates with Enterprise Manager (I did not see this integration though)
Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!
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.
Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in WSO2. But Sentinel is really expensive... Mulesoft: Nice and clean. Again, no expert knowledge needed of how the product works internally. Like using word... or any other application, except WSO2. Have java developers never heard of exposing configurations through a user inyterface?? Mulesoft, however is really expensive. Azure: Not cheap!! And a chaotic interface too. But it pays! If you have a Microsoft account already, this is your next step. We chose WSO2 4 years ago because it was free... but we're moving to azure now. And we're very happy with that decision.
Overall, the client is pleased with the API Manager. They are rather new to it so the ROI has not really been realized yet
They like the ability to monitor the API's utilization (this monitoring could maybe be used for the prior question on usage billing...they do not currently do this for their supported applications)
They like the ability that the APIs can be secured. Just because it exists, doesn't mean it can be used just anywhere...
