![]() ![]() In fact, AWS specifies no limits in terms of connections per second or concurrently in the service quotas page. In practice, it’s risky to rely on it for purposes that involve user-facing endpoints.ĪLB, on the other hand, is virtually unlimited. ![]() However, AWS does not take any hard commitments, and developers can’t control or predict how the burst capacity will be allocated. The 10,000 limit also benefits from burst capacity – up to 5,000 additional RPS – in peak demand moments. More troublesome is that the last two can’t be increased, while the larger quota can on a per-request basis. When we look at Regional and Edge APIs, the limit is a lot more concerning: 600 and 120, respectively. For high-throughput applications, though, there are differences that need to be considered.ĪPI Gateway has a limit of 10,000 RPS (requests per second), which might not be enough for some cases. Scalabilityīoth are highly-scalable services to a point that scalability should not be a concern for most use cases. In this article, we will dive into more details on how these two types of HTTP networking services compare, using the AWS services as a base level: API Gateway and Application Load Balancer (ALB). But how should we choose which one to use? The answer is yes and, in many cases, they are substitutes for each other. ![]() We recently wrote about whether API Gateway can act as a Load Balancer. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |