<story><title>Amazon API Gateway – Build and Run Scalable Application Backends</title><url>https://aws.amazon.com/blogs/aws/amazon-api-gateway-build-and-run-scalable-application-backends/</url></story><parent_chain><item><author>andybak</author><text>I&amp;#x27;ve not tried very hard but I&amp;#x27;m not sure I get it.&lt;p&gt;I&amp;#x27;ve got an API already running. What does this buy me?&lt;p&gt;Caching? I can see some benefit there it&amp;#x27;s read heavy.&lt;p&gt;Auth and access control? Feels like that&amp;#x27;s part of my app code but maybe there&amp;#x27;s a benefit I&amp;#x27;m missing&lt;p&gt;A lot of the other benefits also feel like it would be hard to cleanly separate them from my app code.&lt;p&gt;What&amp;#x27;s the elevator pitch and who&amp;#x27;s the target market?</text></item></parent_chain><comment><author>jively</author><text>API Managmeent market is quite big, makes sense for Amazon to get on board.&lt;p&gt;Imagine this: You are BigCorp USA Inc. and have a bunch of internal SOAP-based web services that are 10 years old and cost a fortune to maintain.&lt;p&gt;You hear someone will pay you to use them, but SOAP sucks. So you could either go and change your APIs (and probably break a bunch of internal processes) OR you could use a gateway to sit in front of them and translate in bound &amp;#x2F; outbound requests. Now you can charge people for your APIs!&lt;p&gt;Scenario 2: If you&amp;#x27;re an indie dev&amp;#x2F; startup but dont want to run EC2 infrastructure, Lambda + Gateway = Cloud service, without any heavy lifting, servers and cost effective. It&amp;#x27;s development lego. Kind of like Parse.&lt;p&gt;Scenario 3: You have an API for your app, now you wnat third party devs to use it.Your API is not set up for that kind of access (multi-user security, throttling, quotas, analytics etc.) - solution: shove a gateway in front of it.</text></comment>
<story><title>Amazon API Gateway – Build and Run Scalable Application Backends</title><url>https://aws.amazon.com/blogs/aws/amazon-api-gateway-build-and-run-scalable-application-backends/</url></story><parent_chain><item><author>andybak</author><text>I&amp;#x27;ve not tried very hard but I&amp;#x27;m not sure I get it.&lt;p&gt;I&amp;#x27;ve got an API already running. What does this buy me?&lt;p&gt;Caching? I can see some benefit there it&amp;#x27;s read heavy.&lt;p&gt;Auth and access control? Feels like that&amp;#x27;s part of my app code but maybe there&amp;#x27;s a benefit I&amp;#x27;m missing&lt;p&gt;A lot of the other benefits also feel like it would be hard to cleanly separate them from my app code.&lt;p&gt;What&amp;#x27;s the elevator pitch and who&amp;#x27;s the target market?</text></item></parent_chain><comment><author>_pius</author><text>This is a pretty big deal, even if just for the fact that this plus Lambda eliminates fixed costs.&lt;p&gt;Rather than running an API server 24&amp;#x2F;7, you can write your API as a set of functions that cost you money only when they&amp;#x27;re actually invoked.</text></comment>