Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management.
Reducing development hours from eighty to four for an API was possible due to reusing existing scripts from DataPower.
Proper configuration of the solution, implementation strategy and correct scaling tier selection are other factors that influence the ROI.
It helps connect all multi-environment applications to a single dashboard and give beautiful reports.
If I am working in AWS and with Azure, I see that Azure is much easier and helps save time while also being able to manage and deploy the API services.
They are responsive and provide assistance even during production issues.
The customer service and support are cooperative and effective in providing insights and solutions during challenges.
Support is excellent when it comes to APIC.
We have regular sessions with Microsoft where we can have private previews of new features.
I rate the support from Microsoft Azure API Management a ten out of ten.
The documentation from Microsoft helps our company to solve issues on our own.
Adding extra Cassandra databases is complex.
With container versions, scaling up or down the gateways deployed into pods is a two to three-minute task for the operations team.
I rate the scalability of Microsoft Azure API Management a ten out of ten.
It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow.
There are no limitations to adding any number of devices.
Apigee is stable, and we have had the system running on Apigee servers for more than four years without any stability issues.
The runtime engine for the APIC Gateway is still a DataPower component, which has been stable in the industry for about fifteen years.
This is the best service we have used within Azure and it has high availability.
I can't guarantee its stability or flexibility until all our databases and financial systems are integrated.
Microsoft Azure API Management is very stable.
Apigee only allows validation of transactions up to a four-hour period, which requires manual hovering over the date and time.
Analytics is one of the areas needing enhancement, specifically more visibility and control over traffic to improve capacity management and high availability.
Apigee should also incorporate these capabilities, especially in the on-premises version.
Examples include the lack of connectivity to MQ.
The service is extensive and expensive, and this added flexibility would make it more manageable and less prone to errors.
It's quite expensive, which could be a barrier for some users.
Documentations for the product should include examples of implementation.
Apigee is perceived as slightly costly compared to other tools in the market.
Apigee is high-priced, suitable for large enterprises where the benefit aligns with the cost.
Apigee is costlier compared to other solutions.
Pricing depends on how many instances run across environments.
The solution is highly expensive.
It's an expensive solution.
However, once you scale up to your full volume, it'll be more expensive.
It provides all the necessary capabilities for current technologies, enabling communication and translation between protocols, along with supporting stringent security features.
The features for API security have been significant with Apigee.
Apigee provides catalog management, onboarding of new customers, an API portal, and security features.
It offers significant development efficiency, reducing man-hours from eighty to four when creating APIs.
The platform's most valuable features are its rule-based permissions and comprehensive API lifecycle management capabilities.
The ability to create a subscription model for APIs allows companies to monetize valuable data and share it securely.
The analytics phase of API Management is very beneficial for tracking API usage and identifying suspicious users.
Apigee is a platform for developing and managing APIs. Apigee offers an interface for your core services by wrapping them with a proxy layer which is then accessed by other developers. With Apigee, you can design and build APIs and then securely share their services and data without exposing any code.
Because app developers make HTTP requests to an API proxy rather than directly to your services, your services are separated from the developers. All the developer needs to know is the URL of the API proxy endpoint, necessary query parameters, authorization credentials (if they exist), and the response data format.
The API proxy isolates the app developer from your backend service. Therefore, you are free to change the service implementation if the public API remains consistent. By maintaining a consistent frontend API, existing client apps will continue to work regardless of changes on the backend.
Key capabilities of the Apigee API management platform include:
Reviews from Real Users:
Apigee stands out among its competitors for a number of reasons. Several major ones are its rich developer portal, its advanced analytics, and its central monitoring system.
Carlos R., a software architect at Caja Los Andes writes, “The central monitoring feature is the most valuable. It also provides security for the APIs and high availability for our use cases. Apigee is the best product in the industry in comparison to other API management solutions. It helps in fast development, which is a top point. It also supports a lot of industry standards and has excellent documentation.”
An associate vice president at a tech services company notes, “The analytics function and the developer portal are the two valuable features of Apigee. The analytics part is very good, and the developer portal is quite rich in features. The authentication mechanisms are quite easily built into Apigee, which is something that most of the other products have also now started supporting.”
IBM API Connect facilitates API management and integration in the financial sector. Companies use it to expose, secure, and manage APIs for banking, insurance, and fintech, deploying it on-premises, in the cloud, or as a hybrid solution.
IBM API Connect focuses on creating and monetizing APIs while enabling seamless transactions and integration with third-party services. It is vital for compliance with regulations and enhances external communication among institutions. With deployment options suitable for different environments, it supports centralized gateway management, robust security features, and comprehensive API lifecycle management. Users benefit from powerful analytics, user-friendly interfaces, and high performance with capabilities in message transformation and efficient monitoring.
What are the most important features?IBM API Connect is extensively implemented in the financial sector, enabling banking, insurance, and fintech services to manage APIs efficiently. Companies use it to ensure secure transactions, integration with third-party services, and compliance with regulatory standards. Its deployment flexibility accommodates different infrastructure needs, making it suitable for a wide range of financial applications.
Microsoft Azure API Management is essential for managing APIs, facilitating integration, and ensuring secure internal and external communication.
Organizations leverage Microsoft Azure API Management for seamless integration and effective API management. It supports microservices, legacy modernization, and platform orchestration in sectors like healthcare, telecom, and finance. Features such as developer portals and centralized libraries simplify usage. While it showcases strengths in hybrid cloud support and scalability, improvements are suggested in versioning and multi-tenancy.
What key features does it offer?Microsoft Azure API Management aids modernization across healthcare, telecom, and financial services by enabling legacy system updates and facilitating smooth platform orchestration.