Im pretty sure there are tools dedicated to do just that task (hint: aws.amazon.com/eventbridge/ ). S3 is a file storage.
I wouldnt recommend someone hacking infrastructure to save 3$ a month, just focus on your core business and go from there, because cost of hacking, long term, is usually far more than you could possibly ever save on it. Not to mention, you have to maintain and fix when it breaks.
Yup EventBridge is yet another way to get an event bus up and running within AWS. I don't think there is any mention of hacking mentioned in here or cost saving for that matter. This is just a thought experiment on how it could be mimicked using S3. I have actually seen this idea applied within Fortune 100 companies (pre EventBridge).
Yeah, exactly. Fortune 100 companies have 1000s employees, "your new startup" that someone will start, will have none, or best case scenario couple. They should definietly not fiddle with adapting s3 to eventbridge or DB, as some people try to do.
I think the issue is that this article reads as if it were a recommendation. Maybe in large part to the title referencing "your next architecture" as if it is something one should implement. I do think S3 events are useful, but I wouldn't use them as a bus for a system that wasn't already focused on the data being put in the S3 :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Im pretty sure there are tools dedicated to do just that task (hint: aws.amazon.com/eventbridge/ ). S3 is a file storage.
I wouldnt recommend someone hacking infrastructure to save 3$ a month, just focus on your core business and go from there, because cost of hacking, long term, is usually far more than you could possibly ever save on it. Not to mention, you have to maintain and fix when it breaks.
Yup EventBridge is yet another way to get an event bus up and running within AWS. I don't think there is any mention of hacking mentioned in here or cost saving for that matter. This is just a thought experiment on how it could be mimicked using S3. I have actually seen this idea applied within Fortune 100 companies (pre EventBridge).
Yeah, exactly. Fortune 100 companies have 1000s employees, "your new startup" that someone will start, will have none, or best case scenario couple. They should definietly not fiddle with adapting s3 to eventbridge or DB, as some people try to do.
I think the issue is that this article reads as if it were a recommendation. Maybe in large part to the title referencing "your next architecture" as if it is something one should implement. I do think S3 events are useful, but I wouldn't use them as a bus for a system that wasn't already focused on the data being put in the S3 :)