Over a million developers have joined DZone.

Static API Throttling or Elastic API Scaling

· DevOps Zone

The DevOps zone is brought to you in partnership with Sonatype Nexus. The Nexus suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today

Stephen posted a good API architecture question in a LinkedIn group,

So your API management initiative is a success. Now how do you cope with the unpredictable volumes? Throttle requests over static infrastructure or make your next initiative “elastic” infrastructure?

Static API throttling and elastic API scaling are complementary design techniques.

Static API Throttling

Static throttle limits ensure that you can limit aggregate maximum demand and rightsize back-end capacity for worst-case loads. API gateways enforce a choke point that can shape traffic volume and ensure back-end target service infrastructure is not overwhelmed.  Throttle limits may be defined per user and per API, and API traffic routing rules can allocate demand across multiple static service infrastructure environments.

DevOps teams rely on usage monitoring and alerts to help them proactively scale infrastructure components.  With adequate lead time, teams can manually provision additional capacity and scale static environments.

Elastic API Scaling

Elastic infrastructure reduces the lead time required to scale infrastructure up and down, and meet demand.  Elastic infrastructure increases IT resource efficiency and reducing capacity delivery timelines.  When designing an elastic API platform,  consider interactions between API consumers, API delivery networks, elastic load balancers, API gateways, enterprise service bus mediators, and service hosts.

Static or elastic?

Static and elastic are complimentary. Static throttle tiers enable teams to offer their API as a well-defined product offering with expected operating margins. Subscription-based usage monitoring helps teams track API usage per customer and understand how to best monetize the API through SLA tiers and charges. Elastic scaling enables teams to open up new API consumer channels "at the speed of now" and offer your business as a service while minimizing IT infrastructure delivery timeline constraints.

Recommended Reading

API Management: A Technical Evaluation Guide

API Management Building Blocks and Business Value

Your API Branding Strategy

Crafting a SaaS API

The DevOps zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today


Published at DZone with permission of Chris Haddad, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}