Serverless Takes DevOps to the Next Level
My real problem with serverless (right now) is that it just destroys your ability to have an efficient development workflow. Unless you want to use the really specific nodejs serverless framework, you&#x27;re really in trouble. (As far as I can tell, <a href="https:&#x2F;&#x2F;github.com&#x2F;dherault&#x2F;serverless-offline" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dherault&#x2F;serverless-offline</a> is the only offline-API-gateway).<p>If AWS really wants to drive adoption of their more-proprietary cloud tech, they&#x27;re going to have to drive harder on local dev workflows. Google is doing better here (e.g. <a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;functions&#x2F;docs&#x2F;emulator" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;functions&#x2F;docs&#x2F;emulator</a> and <a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;pubsub&#x2F;docs&#x2F;emulator" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;pubsub&#x2F;docs&#x2F;emulator</a>) As someone who cares greatly about productive developer environments (it&#x27;s a reasonable portion of my day job), I wouldn&#x27;t touch serverless right now. Things slow down way too drastically if you have to push to the cloud to test what you&#x27;re building.<p>I looked into starting a new app using serverless tech just yesterday. I don&#x27;t really want to use nodejs on the backend (as I can use any language on the backend, and JS is not the pick of the litter), so that left me totally optionless unless I want to build up a bunch of infrastructure on my own (and sometimes I enjoy that, just not my goal right now).<p>As usual, the death of devops is greatly exaggerated, the role will evolve like any other. As the boring stuff gets easy, application complexity will grow. There&#x27;s really still a lot of boring stuff that isn&#x27;t automatically solved for you.