<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Nick Choi &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/author/nick-choi/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Mon, 09 May 2022 14:10:45 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>Throttling a tiered, multi-tenant REST API at scale using API Gateway: Part 2</title>
		<link>https://noise.getoto.net/2022/05/09/throttling-a-tiered-multi-tenant-rest-api-at-scale-using-api-gateway-part-2/</link>
		
		<dc:creator><![CDATA[Nick Choi]]></dc:creator>
		<pubDate>Mon, 09 May 2022 14:10:45 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon API Gateway]]></category>
		<category><![CDATA[Amazon Cognito]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[AWS Amplify]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[SaaS]]></category>
		<category><![CDATA[Software as a Service]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=d01df00ef53dac72b31e574fa0766927</guid>

					<description><![CDATA[In Part 1 of this blog series, we demonstrated why tiering and throttling become necessary at scale for multi-tenant REST APIs, and explored tiering strategy and throttling with Amazon API Gateway. In this post, Part 2, we will examine tenant isolation strategies at scale with API Gateway and extend the sample code from Part 1. […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Throttling a tiered, multi-tenant REST API at scale using API Gateway: Part 1</title>
		<link>https://noise.getoto.net/2022/05/06/throttling-a-tiered-multi-tenant-rest-api-at-scale-using-api-gateway-part-1/</link>
		
		<dc:creator><![CDATA[Nick Choi]]></dc:creator>
		<pubDate>Fri, 06 May 2022 17:28:25 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon API Gateway]]></category>
		<category><![CDATA[Amazon Cognito]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[AWS Amplify]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[SaaS]]></category>
		<category><![CDATA[Software as a Service]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=935ba55d0c6fe357b83a9288a4a0fba3</guid>

					<description><![CDATA[Many software-as-a-service (SaaS) providers adopt throttling as a common technique to protect a distributed system from spikes of inbound traffic that might compromise reliability, reduce throughput, or increase operational cost. Multi-tenant SaaS systems have an additional concern of fairness; excessive traffic from one tenant needs to be selectively throttled without impacting the experience of other […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 29/71 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2026-03-11 08:03:19 by W3 Total Cache
-->