It's interesting, because as the Serverless space evolves there are two emerging sales and marketing tracks for the technology: (A) This will reduce your costs

It's interesting, because as the Serverless space evolves there are two emerging sales and marketing tracks for the technology: (A) This will reduce your costs (CIO Track) (B) This will reduce your time to market (PM / Developer Track) Amiram's article here clearly tries to deconstruct the argument in (A) and suggest, well, it's more expensive than you think (and Spotinst is the cheapest option - kudos to Amiram and team) which... is undeniably true, and API Gateway is a large part of that. It seems based on Re:invent 2017 in November that Amazon is moving to target the (B) track more aggressively, which is where we've been residing in a niche with StdLib since we launched [0]. Realistically I think both tracks are actually half-truths (as is all marketing), as Amiram even touches on re: lines of code written to maintain Serverless architecture. At the end of the day, Serverless technology is going to open up a world Simon Wardley [1] has painted a picture of: one of reliable, fault-tolerant, self-healing, predictably priced service composition that can be performed by developers who are increasingly unaware of implementation details, and perhaps not even developers in the traditional sense. It's been a neat exercise at StdLib trying to find the intersection between current development paradigms (old hat monoliths, etc.), the utility / lower cost / lower time to delivery of serverless tech, and the future of emergent, unexplored markets. As the marketing sizzle of "serverless" begins to fade (it hasn't peaked yet, but it will), and we see more challenges to the technology itself, it will be interesting to see what business practices and development paradigms pop up around serverless architectures, and how companies begin maximizing the utility of a new development canvas. One day it won't be "serverless," it will simply be best practice for most companies to ship application logic directly to the runtime layer. What does that world look like, where will costs (/prices) settle, and how do all players in the market continue delivering the most value to developers and companies? It'll be neat to watch it all play out, to say the least. [0] https://stdlib.com/ https://stdlib.com/ [1] http://blog.gardeviance.org/2016/11/why-fuss-about-serverless.html http://blog.gardeviance.org/2016/11/why-fuss-about-serverles...