1. 6


    The serverless concept solves this problem, because it requires no DevOps to build and deploy applications at scale. But so far, this kind of technology has only been available exclusively from cloud vendors, like AWS, Azure and Google Cloud Platform, forcing users into proprietary technology and having no freedom to run it in private clouds or locally, for development.

    …makes no sense. What can serverless possibly mean if you run it on your own servers? What is zero DevOps involvement with a new server-side tool that must be configured to run applications? What is the sound of one hand clapping?

    The serverless concept moves the problem, often to an unexpected place.

    1. 2

      Hey there, author here. I was just saying that DevOps don’t intervene in the building / deployment of individual apps. DevOps do very much need to exist to maintain the platform itself. It just decouples things and thus reduces the amount of hand-holding.

      1. 4

        Thanks, that’s a useful clarification. I do think that some amount of hand-holding is important for its own sake; Allspaw and Hammond’s 2009 description of DevOps focused more on empathy and cooperation between developers and operations folks than on decoupling or hand-offs. If you don’t want to hold hands then a 3rd party commercial platform like Heroku is very appropriate.

    1. 1

      It seems like you can only write apps in JS with this. Is that true?

      1. 2

        For now Go and JS are supported. Python and Java are coming next. It’s based on gRPC so adding new languages is relatively easy.