I'm planning on the following for a use case scenario for AWS Lambda and want to make sure I'm headed in the right direction and that there's not some better/easier solution out there.
The database is in AWS RDS (SQL Server), and the web application is in AWS ECS Fargate / Dockerized. The database has ~8,000 records in it. Language wil be .NET Core 3.1 / EF Core 3.1 (when it is supported here shortly hopefully).
What needs to happen is every day something wakes up and gets the IDs of the records that need to be updated today (those that have not been updated in a month). Each of those IDs are sent to a remote API and the results used to update the original database record.
For this I am thinking I can use two Lambda functions?
AWS Docs say you can run up to 1,000 Lambdas as a time (and request more if you have to), so that should be sufficient for my needs at the moment.
- Wakes up and gets the list of IDs
- For each ID, spawn Function 2 and pass along the ID
- Receive the ID of the record to update
- Make a call to the remote service to get the updated data for ID
- If success update the database fields and LastUpdated date for ID
- If error mark record as error/retry
This seems like what Lambda was made for to me? Am I wrong or overlooking something basic that will bite me when I start?