Rebuilding Bloated cron jobs with Event Bridge

Preface of something that barely exists, as everything is a simulation, innit? I should grab your attention with the best and most sophisticated words created by top-notch AI; nevertheless, I hope you if you exist prefer more organic and crafted posts (considering the numerous posts produced directly from the dark forest). Yeah, I also know about the thrive in obscurity and sometimes I find myself reflecting on the future and how it might be gazing into the abyss without anyone caring about what I do. I'm trying to push myself out and shout to an audience that might not even exist. Moreover, I should probably be sleeping instead of writing this down, hehe Back from the reverie, let's talk about re-architect something Recently, I was refactoring a cron job that ran every hour, every day, to obtain lab results from a laboratory provider that lacked a webhook to notify us when a laboratory checkup result was ready. So the outsourcing engineers from the beginning era created a bloater, basically a HUGE lambda with 10 gigs of memory and 15-minute timeout in a x86 architecture, to process all the appointments and try to find a lab result, as this was made without caring about the scale that this has now. Consequence: The lambda hourly times out without processing the entire appointment list, and most of the time repeats from the beginning of the list without any "bookmarks"

Jun 25, 2025 - 06:40

Rebuilding Bloated cron jobs with Event Bridge

Preface of something that barely exists, as everything is a simulation, innit?

I should grab your attention with the best and most sophisticated words created by top-notch AI; nevertheless, I hope you ~~if you exist~~ prefer more organic and crafted posts (considering the numerous posts produced directly from the dark forest). Yeah, I also know about the thrive in obscurity and sometimes I find myself reflecting on the future and how it might be gazing into the abyss without anyone caring about what I do. I'm trying to push myself out and shout to an audience that might not even exist. Moreover, I should probably be sleeping instead of writing this down, hehe

Back from the reverie, let's talk about re-architect something

Recently, I was refactoring a cron job that ran every hour, every day, to obtain lab results from a laboratory provider that lacked a webhook to notify us when a laboratory checkup result was ready. So the outsourcing engineers from the beginning era created a bloater, basically a HUGE lambda with 10 gigs of memory and 15-minute timeout in a x86 architecture, to process all the appointments and try to find a lab result, as this was made without caring about the scale that this has now.

Consequence:

The lambda hourly times out without processing the entire appointment list, and most of the time repeats from the beginning of the list without any "bookmarks"