The
API Gateway?
API Usage Boom
#1 Iteration #2 Iteration #1.0 Release #2.0 Release
A bit of history
• Configuration
stored in JSON
• Some scaling
related issues
• Keys stored in
SQLITE
• Throttling rules
enabled based on
memcached.
• VCL used for
configuration
• Central
management
node
• Fully api-driven
• Web UI
• Improved
performance
• Bundled CLI • Improved access
control model
User
API
Store
API
Billing
API
Search
API
Consumer Consumer Consumer
Consumer Consumer
API Manager
Security
Throttling
Routing
Metrics
Consumer
Consumer Consumer
Varnish
Cache
Varnish
Cache
Varnish
Cache
API Engine Processing Layer
User
API
Store
API
Billing
API
Search
API
API Endpoints
Throttling
(memcached)
Statistics
(VCS)
Management
REST API
Administrators
Management
User
API
Store
API
Billing
API
Search
API
Varnish
Cache
Throttling
(memcached)
Statistics
(VCS)
Management
REST API
Varnish
Cache
Varnish
Cache
Administrators
Consumer
Consumer Consumer
API Engine Processing Layer
API Endpoints
Management
Varnish Cache Node
Varnish
Cache
API Engine
VCL
KVstore and
SQLite VMODs
Memcached
VMOD VCS
probe
syncd
DB
Core functionality
• Authentication and authorisation (security)
• Statistics (metering)
• Throttling (rate limits)
• Load balancing and routing
• Caching reads
Demo
Api-Engine & Locust
http://locust.io/
Thank you

API Engine