title: Is having multiple lambdas chain calls a bad idea?
body: <p>We are currently using serverless framework for our microservices, currently each services is stored in a single big lambda that handle many types of requests.</p>
  
  <p>It seems that the standard is to have a lambda per request type, so each of our servers would end up being broken up in many pieces.</p>
  
  <p>I am afraid that if I have to call other of these new functions I would end up chaining invocations (and thus paying for a lot of lambdas that are waiting).</p>
  
  <p>How do you tackle this?</p>