Ali Haydar

Hey Igor, thanks for this feedback, and for the awesome knowledge you shared.

Totally agree with everything you mentioned, and appreciate bringing up the lambda scalability, which I did not take into consideration.

We can with the current design of the DynamoDB to query it and stop using scan, and this in fact is directly related to the fix of filtering public companies. However, I would love to hear your thoughts on the schema, would you suggest any changes on the current implementation? Here's a quick summary of the current implementation:

```a partition_key that would contain the company id ( , a sort_key that would contain whether the company is private or public.```

Would you please elaborate on this point: `One other consideration is how long Dynamo call takes and if behavior of the SDK calling Dynamo needs changing.` ? is it also related to not using "Scan"?


Software engineer (JS | REACT | Node | AWS | Test Automation)