Timeline for Most elegant way to execute a AWS lambda function with preloaded parameters on a specific time
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 8, 2016 at 12:18 | comment | added | Jean Lbr | @DanPichelman We're talking about few hundreds (maybe few thousands in a couple of months) entries in the table and the exactitude span should be between minutes and hours. | |
| May 8, 2016 at 12:14 | comment | added | Jean Lbr | @JeffO Here is what I found: alestic.com/2015/05/aws-lambda-recurring-schedule Clearly after few more readings, I think the correct approach is to execute a lambda recurrently and check if I need to switch the status from active to done on all the rows of the table that are marked as active | |
| May 6, 2016 at 16:23 | comment | added | Dan Pichelman | Also, how 'exact' do you need to be? Within a couple of hours? a couple of minutes? no more than 10 milliseconds from the end_date? | |
| May 6, 2016 at 16:22 | comment | added | Dan Pichelman | How many entries in the database are we talking about? The right answer for 20 records won't be the right answer for 20,000 or 20 million. | |
| May 6, 2016 at 15:50 | comment | added | JeffO | Can you share what you found on Google? It may improve the answer to show how to make a minor change instead of creating a whole new example? | |
| May 6, 2016 at 15:31 | review | Close votes | |||
| May 26, 2016 at 3:02 | |||||
| May 6, 2016 at 15:18 | answer | added | Daniel777 | timeline score: -2 | |
| May 6, 2016 at 14:48 | history | asked | Jean Lbr | CC BY-SA 3.0 |