Architecture
Cloud-native (Google Cloud), uses distributed architecture for auto-scaling
Cloud-based iPaaS (Integration Platform as a Service) with a distributed architecture using Atoms for execution
Built on NGINX/LuaJIT, lightweight and high-performance with etcd as a storage center
API Management Capabilities
Full API lifecycle management, but relies on the Google Cloud ecosystem and less focus on deep system integration
Offers API management through its API Control Plane with centralized governance
High-performance API gateway, extensible via plugins, cloud-native friendly, flexible enough to be integrated with third-party tools for extendibility
Performance & Scalability
Cloud-based auto-scaling, is dependent on Google Cloud infrastructure
Optimized for mid-sized integrations but struggles with high-volume API traffic
Built on Apache APISIX, ultra-high performance, excels in high-traffic scenarios, and is horizontally scalable and Kubernetes-native
Deployment Flexibility
Cloud-native (Google Cloud) with hybrid support via Apigee Hybrid but the initial setup can be complex
Cloud-native with hybrid deployment options using on-premise agents
Easy installation with flexible deployment, supports multi-cloud, hybrid-cloud, and edge environments
Integration Complexity
Requires improvement in integrations, including that with IdP and standard integration capabilities needed for banking or retail sectors
Strong and quick integration capabilities with extensive pre-built connectors and a low-code approach
Flexible enough to be integrated with third-party tools for extendibility, allows for custom integrations and extensions through its plugin ecosystem
Protocol Support
REST, SOAP, GraphQL, OData, gRPC, OAS 3.0
Primarily supports REST and SOAP APIs
Broad support (REST, gRPC, MQTT, WebSocket, Kafka)
Cost Structure
Subscription-based, costs scale with traffic, but can be expensive for enterprises with high traffic with analytics and security as add-on fees
Flexible and operational costs rise with usage, and high expenses for complex workflows
Low total cost of ownership due to its open-source core, pay-for-support model, cost-effective at scale
Vendor Lock-in
Tightly integrated with Google Cloud infrastructure while hybrid deployments still rely on Google Cloud control plane
Cloud-native but tied to AWS/Azure ecosystems, limited portability for on-premise or multi-cloud strategies
Based on Apache APISIX, which is fully open source and licensed under the Apache 2.0 License, Kubernetes-native and multi-cloud friendly
Plugins
Custom JavaScript/Java policies and limited pre-built plugins while offering a range of built-in policies that function similarly to plugins
Extensive library of pre-built connectors and integration packs
Open-source plugin ecosystem, including custom plugins, security, observability, and authentication, and allows plugin development in multiple languages
Security
Advanced threat protection, OAuth, JWT, and Google Cloud security integration
Basic security features including OAuth, JWT, and API keys
Supports JWT, OIDC, OAuth2, IP whitelisting, mTLS, and FIPS 140-2 compliance
CI/CD Integrations
Offers API-first CI/CD, REST APIs for deployment automation, Terraform support
Limited CI/CD integration capabilities
Declarative YAML/JSON configurations, Helm charts for Kubernetes, offers native integration with ArgoCD, Jenkins, and GitHub CI/CD
Community Support
Official Google Cloud support, forums, and paid SLAs, limited open-source contributions
Active community within the Dell ecosystem, but the response time could be faster
Active open-source Apache APISIX community, vendor-backed enterprise support with contributions to the Apache project