May 6 · 6 min read · Synchronous Architecture Consider a simple example of a user creating an application which has the following steps: User sign's up Insert User in DB Send a Welcome Email to the User Create Token
Join discussion
Feb 1 · 6 min read · If cron has a single moral lesson, it’s this: time does not guarantee uniqueness. Jobs run twice. Or zero times. Or half a time. Or later than expected. Cron does not promise exactly once execution, and every system that assumes it does eventually pa...
Join discussion
Jan 25 · 6 min read · Up to this point, the series has talked about cron in abstractions: principles, patterns, framework intent. This article steps out of theory and into a specific, imperfect reality. What follows is not a reference architecture or a recommendation to c...
Join discussion
Jan 25 · 6 min read · By the time a system reaches production, most architectural mistakes don’t announce themselves loudly. They surface as unease. As dashboards that look fine but feel wrong. As bugs that appear only at certain hours. As jobs that “usually” run. This ar...
Join discussion
Jan 18 · 6 min read · At first glance, HumHub’s cron setup looks almost suspiciously simple. Two commands. Run every minute. No fancy schedules. No visible orchestration logic. If you approach it expecting a clever optimization, you might be tempted to “improve” it. Split...
Join discussion
