I understand this concern.  This is where JAWS comes in.  The best way to do Lambda development, is to make AWS Lambda a thin wrapper around your own separate code, to keep that code re-usable, testable and AWS independent.<p>JAWS generates scaffolding to encourage this for you.  As a result, your code ends up looking just like a traditional application framework&#x27;s code.<p>I just did a talk on JAWS @ Re:Invent to over 600 people.  The line was out the door.   Honestly, I didn&#x27;t hear &quot;I&#x27;m only going to use this for a hackathon project&quot; once, except for now.  Instead, all I heard was, &quot;OMG we don&#x27;t have to deal with servers!!!  We will use this for everything!!!&quot;.  And there were huge enterprise companies there.<p>I&#x27;m a Docker lover, but Lambda has a huge head start in many areas.  Super fast spin-up times, orchestration handled for you, the ability to containerize functions&#x2F;endpoints not just applications, and pay per use pricing.  All of this comes with Lambda out-of-the-box.