With all respect and love to the OP, I must admit that I laughed out loud when I saw the AWS architectural diagram and wondered whether this might be a joke. Personally, I'd have implemented this as a few dozen lines of Python living as a cron job (or even as a long-lived process with a schedule), but I'm no pedigreed engineer.
tr97|1 year ago
delduca|1 year ago
namaria|1 year ago
jedberg|1 year ago
OP actually did it more efficiently than most! You should see the AWS suggested architecture. It uses something like 10 different AWS services.
My company actually set out to solve this very problem. We have a cloud cron hosting that's more reliable than the AWS architecture but just requires a few lines of code. Literally this is all you have to do:
https://github.com/dbos-inc/dbos-demo-apps/blob/main/python/...huijzer|1 year ago
QuinnyPig|1 year ago
IanCal|1 year ago
Cron trigger.
Process.
Gpt API.
Database for persistence.
Email sender.
Which part of that wouldn't you have?
singron|1 year ago
behnamoh|1 year ago