Stateful Application: AWS Lambda vs Lolo Code

╔════════════════════════════════════════╦════════════════════════════════════════════╗
║               AWS Lambda               ║                  Lolo Code                 ║
╠════════════════════════════════════════╬════════════════════════════════════════════╣
║ - Lambda's programming model is        ║ - Lolo supports application state and the  ║
║ stateless.                             ║ state can be retrieved and updated by      ║
║                                        ║ all the functions in the Lolo application. ║
║ - But lambda can access stateful data  ║                                            ║
║ from stateful services such as         ║ - Ran both stateful and stateless          ║
║ Dynamo DB and Redis.                   ║ application in Lolo, there wan't a huge    ║
║                                        ║ difference in the response time.           ║
║                                        ║ Stateful API call took 5-10 ms more to     ║
║                                        ║ respond.                                   ║
╚════════════════════════════════════════╩════════════════════════════════════════════╝