Question: Give me a bullet point list of all decisions to use Aws Lambda to build Devflows with the date on which the decision was made
Answer: Decisions to use AWS Lambda to build Devflows include:
Decision to use AWS Lambda to build Devflows made on Week 33, 2021 (source: 4)
Decision to change the abstraction to run on Lambda (date unknown) (source: 3)
Decision to update every action to be compatible with Lambda (date unknown) (source: 3)
Decision to introduce the concept of “functions” to work on Lambda (date unknown) (source: 3)
Decision to make each proxy a Lambda function, triggered from SNS and firing the next event to SNS when the action completes (source: 11)
Decision to use an API model in TypeScript, deploy in Lambda, and handle the DevFlows platform work in a Lambda layer (source: 11)
Decision to combine multiple Actions into a single Lambda function as an optimization (source: 11)
Some of the intermediate steps contains (unknown dates)
A part is show below:
Bullet point list:
- Decision to use AWS Lambda to build Devflows (date unknown)
- Change in abstraction to run on Lambda (date unknown)
- Update of every action to be compatible with Lambda (date unknown)
- Introduction of concept of “functions” to work on Lambda (date unknown)",
All the document metadata is in there with the chunk, we lose the date information in the reduce step.
Random source numbers don't occur in intermediate steps and come due to the combining step.
Question: Give me a bullet point list of all decisions to use Aws Lambda to build Devflows with the date on which the decision was made Answer: Decisions to use AWS Lambda to build Devflows include:
Some of the intermediate steps contains (unknown dates) A part is show below:
All the document metadata is in there with the chunk, we lose the date information in the reduce step. Random source numbers don't occur in intermediate steps and come due to the combining step.