aslom

Very good talk. I learned about practical side of running code in AWS Lambda (black) box with peeking inside to fix problems - I need to try lambda-shell. And I enjoyed the 2001 theme though too bad that animations do not work in SlideShare.

The main point of serverless is cost - it is not just "Reduced operational cost" but orders of magnitude difference if one were to build cloud solutions that can scale the the same level and pay for cloud infrastructure (even if not used at minimum something must be running ...), monitoring, and people effort involved on ongoing basis (real cost)

Compare to working with level of abstraction of "entity" (function, could be bigger) and have it running when needed and scale as needed.

I agree with the argument: developers like reading web pages that describe how to use API, covering rationale of API design, gotchas, code samples.

However, what if the specs were able to capture what is in such human-readable pages (for example https://docs.cloudant.com/)? What if API spec could be automatically derived out of HTML pages? Embed some metadata in HTML page and then we have both cake (human-readable) and eat it (machine-readable)?