Timeline for Scheduled AWS Lambda to Update Database via API Call
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 31, 2019 at 19:59 | vote | accept | FirstDivision | ||
| Dec 31, 2019 at 19:51 | history | edited | FirstDivision | CC BY-SA 4.0 | added 91 characters in body |
| Dec 31, 2019 at 19:42 | answer | added | JimmyJames | timeline score: 3 | |
| Dec 31, 2019 at 18:21 | comment | added | FirstDivision | Mostly because I assumed efficient use of Lambda would be to limit the amount of time any single Lambda function would need to run, and that having it do "one thing" was also closer to the suggested architecture / design. | |
| Dec 31, 2019 at 16:15 | comment | added | JimmyJames | Is there a particular need to spawn a new lambda for each ID? This could add some significant overhead. Have you considered passing a list of ID to the second function? | |
| Dec 31, 2019 at 16:00 | review | First posts | |||
| Dec 31, 2019 at 21:18 | |||||
| Dec 31, 2019 at 15:59 | history | asked | FirstDivision | CC BY-SA 4.0 |