Oracle API Platform Cloud Service Reviews

In our organization, we use Oracle API Platform Cloud Service primarily to host and manage our middleware APIs. Our middleware APIs are registered on this platform and exposed to a fixed domain, which supports our organizational goals effectively.

Since our enterprise has many APIs, Oracle API Platform Cloud Service helps us maintain all of our APIs, secure them, and build our applications around that. We are able to monitor the APIs with the features that the platform offers. The cost and maintenance aspects are quite manageable.

Oracle API Platform Cloud Service's UI is quite user-friendly and supports a hybrid deployment model. Oracle API Platform Cloud Service was picked up by some of my former colleagues some years ago before I started working on that product.

The product has features like it can run hybrid. With Oracle API Platform Cloud Service, you can run gateway nodes wherever you want to. I personally feel that the product is quite heavy. Its policy package is nothing beyond or more exceptional than any other vendors in the market.

Oracle API Platform Cloud Service has this gateway which runs as an application inside the WebLogic server. The WebLogic server itself is quite huge. They should have something very lightweight to run this gateway, like NGINX. Right now, it's quite heavy. Oracle API Platform Cloud Service provides an API documentation tool, which is quite outdated. They support more of a blueprint while the market goes with OpenAPI.

We use it for both internal purposes and in cases where there are third-party integrations.

We primarily use it for logging with a third-party logging tool, log notifications, and some custom functions.

API security features within Oracle API Platform Cloud Service are okay. I am satisfied with the API security features within Oracle API Platform Cloud Service.

The analytics features are also helpful in the Oracle's API platform. The log analytics are quite good. They provide detailed logs, making it simple to pinpoint issues and troubleshoot. The analytics are well-presented.

Additionally, I find the customizable dashboards convenient. When you have a privatized dashboard, it's easy to log in, get an immediate snapshot of what's happening, and quickly address any problems.

API Platform is used to manage and monitor APIs as they are published to consumers, both internally and externally to the organization. The cloud service allows us to register all of our APIs as a catalog, link to the Apiary documentation for each API, apply policies (security and usage restriction) to the runtime endpoints, and monitor usage through analytics.

The API Platform has provided a consistent place to administer OAuth 2.0, Access Key, and other policies across groupings of APIs. It has also allowed standardization in the definition and documentation of the APIs. Rather than APIs being documented in a Wiki and shared through ungoverned Postman collections, we can have more fine-grained access and authorization rules as to who can use which APIs. All API usage is now governed and tracked.

API management to public and internal services. Supporting a microservice model so that the microservices dont get accidentally bound together.

The primary goals are:

-Security

- Audit

- Measurement of service utilization

- Accelerate digital enablement

Agility and ease of establishing new APIs and configuration.

Deployment processes far simpler than other Oracle middleware tech such as SOA for example

We use the solution to manage APIs.

The solution's cost in terms of scaling could be better.

Since I see API Management as a key enabler for digital transformation and for growing new digital economies, an consistent API Management strategy is important to define. Consequently, an API Management platform is an essential architectural component in today's applications architecture, which needs to be capable for covering the complete API lifecycle from definition to retirement, supporting an API-First development approach, because with that development of new services and functionalities can be done more efficient.

With API-first, the platform provides a consistent and comprehensible philosophy. It definitely influences:

• The way we think how APIs should be developed.
• What API Management means from a implementation perspective.
• What API Management means from an organizational perspective.

We are using this solution for our providers in Sweden.

Several business functions are exposed to various customers, suppliers, and partners. Oracle API is used to expose their critical business functions to the stakeholders.

We were using an interface for orders where all of the orders that we were receiving were through text-based files from different suppliers, and partners. Now, we have created one order API and exposed it to our various customers. It is also available for our web-based application portal that the other customers were connected to, directly.

They can place orders directly using this API. 

We were not using real-time ordering before this. All orders are now in real-time and we are adding extra features that can tell us who is placing the order and the different levels of access to different types of customers. We can also do direct limiting with API PCS. We have improved our order module with the use of this API.