Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management.
API Gateway saves time and secures my infrastructure, allowing effective deployment.
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.
Most of the time, where we work in companies, it is more of an internal policy or security guidance that we need to have an API gateway.
It helps connect all multi-environment applications to a single dashboard and give beautiful reports.
Within 15 minutes, we had a support engineer allocated via Amazon, and we were able to resolve the issue promptly.
Technical support is excellent, deserving a ten out of ten rating.
You open a chat, have your response, know what to do or what is wrong, and can resolve the problem.
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.
You don't need to worry about the scalability of Amazon API Gateway because AWS takes responsibility for the solution's scalability.
It is very scalable, and we don't need to hire additional engineers.
We've significantly increased our traffic from hitting it once or twice a minute to now hitting it ten to fifteen times within a minute.
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.
You can add more computing power to your APM gateway.
It handles our current workload well, and I'm optimistic it can scale effectively as our needs grow.
I've deployed it for a client with millions of users without issues.
Our applications are stable, owing partly to our architecture, which is spread across three regions.
I've not encountered unavailability or any issue that became a disaster.
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.
A local version of the API Gateway would be beneficial for testing purposes without incurring extra costs.
I would appreciate more comprehensive telemetry information, diagnostics, and improved monitoring capabilities for the services and endpoints.
Apigee has the cloud EPG Microgateway resource, which can be put inside our Kubernetes cluster.
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.
Support for GraphQL, which is a different communication specification, needs to improve.
It's quite expensive, which could be a barrier for some users.
With Amazon API Gateway, you pay for what you use.
However, my understanding is that it easily goes to $14,000 or $15,000 USD each month for each account, and we have several such accounts.
It is a really cheap product, but if used incorrectly, it can become expensive.
Pricing depends on how many instances run across environments.
The more enterprise-level features you go to, the more expensive it gets.
The solution is highly expensive.
It's an expensive solution.
Rest API provides robust and more secure authentication features.
Additionally, it's cost-effective, even as our workload and the number of APIs we manage have increased.
It acts as a master tool, offering easy configuration and excellent integration capabilities with third-party services.
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.
Amazon API Gateway facilitates internal APIs exposure to external users, manages requests, and enhances security with authentication. It efficiently handles serverless architectures with AWS Lambda integration, supporting cloud-based API management.
Amazon API Gateway acts as a gateway for backend microservices, making it suitable for real-time use cases. It enables secure communication, traffic routing, and access control management. With its strength in integrating AWS services, it offers excellent scalability, proxy capabilities, and cost-effective management. Users have noted areas for improvement, such as pricing, interface, and the need for better AI-based capabilities. Improvements are also sought in monitoring, security features, and support services.
What features make Amazon API Gateway stand out?Industries utilize Amazon API Gateway to streamline operations in sectors like finance, healthcare, and tech, focusing on real-time data processing and secure communication. The gateway's ability to manage traffic and provide robust security features is key in industries requiring dependable and versatile API management solutions.
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.
