1. Mastering Performance with IBM API
Connect & DataPower
API Connect & DataPower
Ivan Heninger
Performance
Team Lead
2. DataPower Gateways can deploy anywhere…
Physical appliances: All-in-one (HW / SW), DMZ-ready with physical security including crypto acceleration and
optional hardware security module (HSM)
Software: virtual appliance, application (Linux) & container (Docker) provide flexible deployment options for both
cloud and on-prem environments
2
3. Choosing the right Gateway form factor
Physical appliances provides the most
comprehensive security combined physical
with firmware security.
Virtual, Linux and Container offer “right
sized” units of capacity, as few as 4 CPUs
Container provide ability to leverage auto-
scaling and runtime health monitoring
Container is “cloud ready” to facilitate both
public and private cloud based deployments
4. Natively built API Gateway using
purpose-built technology for native
OpenAPI/Swagger REST and SOAP APIs
Multi-cloud scalability and extensibility
to help meet SLAs and improve client
user experience
IDG X2 physical appliances use the
equivalent of 48 vCPU
Single API Gateway supports 30K TPS with 8 ms latency!
1.6 3.2 1.9 4.7 4.7
15.4
8.2 8.4 8.5 8.7
13.9
43.2
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2 map+invoke+map
8 vCPU map+invoke+map
Latency(mS) @ Min/Max Concurrency
min latency, concurrency 1
max latency, max concurrency(100% CPU)
Max Throughput @ 100% CPU
5. 10X increased performance with natively built API
Gateway for both virtual and physical appliances
Before: DP Multi
protocol Gateway
Service
API call Backend
New: Native API
Gateway Service
API call Backend
10X increased performance with natively built API Gateway
API GW service
6. Benchmark APIs
Invoke
(Simple)
Invoke + Security
(Medium)
Invoke + Transformation
(Complex)
Invoke policy Invoke Policy +
OAuth Security
Map +
Invoke Policy +
Map
Each Benchmark API Assembly includes:
• Rate-limit
• Activity-log
• Client-id validation
Each Benchmark APIs runs with
• 4KB request payload
• Running on IDGX2 and 8 vCPU virtual gateways
7. Single gateway service used for
comparative analysis across three
gateway types:
• API Gateway
• V2018 Multi-protocol Gateway (v5c)
• V5 Multi-protocol Gateway
Backend service simulator is a “no-op”
that delays response using random
uniform distribution between 45 mS and
55 mS
Performance Measurement Details
Load
Drivers
-DP Stone
-Jmeter
V2018.4.1.x
APIC Management
Server and Analytics
8 Core ESX Virtual Gateway
Physical IDGX2 Gateway
V2018.4.1.x Firmware
Back end API service
simulator cluster
V508x
APIC Management
Server and Analytics
V508x
10 Gbps network
1 Gbps network
API-Gateway
V5C
8. API Connect v5084 running with
DataPower version 2018.4.1.1
API Connect V5 with
v2018 MPGW Gateway
8
2759
570
2201
465
1391
256
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2 map+invoke+map
8 vCPU map+invoke+map
Throughput (TPS)
Max Throughput @ 100% CPU
9
18.8 11
29.1
18.8
38.833.2 40.5
123.6
134.2
65.3
138.8
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2…
8 vCPU…
Latency(mS) @ Min/Max Concurrency
min latency, concurrency 1
max latency, max concurrency(100% CPU)
9. 3269
654
2545
527
1478
267
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2 map+invoke+map
8 vCPU map+invoke+map
Throughput (TPS)
Max Throughput @ 100% CPU
API Connect v2018.4.1 with
DataPower version 2018.4.1.1,
running V5c (Multi-protocol
Gateway)
API Connect V2018 with
v2018 MPGW Gateway
9
7.4
16.7 10.1
22.2 18.8
36.2
20.4
27.8
101.1 104.3
58.5
105.9
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2…
8 vCPU…
Latency(mS) @ Min/Max Concurrency
min latency, concurrency 1
max latency, max concurrency(100% CPU)
10. API Connect v2018.4.1 with
DataPower version 2018.4.1.1,
running API Gateway Service
Container form factor has same
throughput and latency
characteristics as Virtual using
same underlying hardware
API Connect V2018 with
v2018 API Gateway Service
10
29932
5144
25571
4271
5088
912
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2 map+invoke+map
8 vCPU map+invoke+map
Throughput (TPS)
Max Throughput @ 100% CPU
1.6 3.2 1.9 4.7 4.7
15.4
8.2 8.4 8.5 8.7
13.9
43.2
IDGX2 invoke
8 vCPU invoke
IDGX2 invoke+Oauth
8 vCPU invoke+Oauth
IDGX2 map+invoke+map
8 vCPU map+invoke+map
Latency(mS) @ Min/Max Concurrency
min latency, concurrency 1
max latency, max concurrency(100% CPU)
11. 10X increased performance with natively built API
Gateway for both virtual and physical appliances
V2018 API Gateway Service vs V5 Multi-Protocol Gateway
Service
13. Notices and disclaimers
continued
13
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products about this
publication and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed
to the suppliers of those products. IBM does not warrant the quality of
any third-party products, or the ability of any such third-party products
to interoperate with IBM’s products. IBM expressly disclaims all
warranties, expressed or implied, including but not limited to, the
implied warranties of merchantability and fitness for a purpose.
The provision of the information contained herein is not intended to, and
does not, grant any right or license under any IBM patents, copyrights,
trademarks or other intellectual property right.
IBM, the IBM logo, ibm.com and [names of other referenced IBM
products and services used in the presentation] are trademarks of
International Business Machines Corporation, registered in many
jurisdictions worldwide. Other product and service names might
be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at “Copyright and trademark
information” at: www.ibm.com/legal/copytrade.shtml.