4 ms·
I never see a blog post looking at the specific requirements of an application and fitting the architecture, data model, and implementation to those requirement
by 0xbadcafebee 4y ago
I never see a blog post looking at the specific requirements of an application and fitting the architecture, data model, and implementation to those requirements. "Monolith vs Microservices" is like saying "18-wheeler vs 20 Toyota Corollas". There are other forms of transportation, and using just one mode may not serve your business well.
By the way, it's 2023... if you have a greenfield project, you should be using event-driven data processing. We got rid of the horse and buggy, let's please get rid of cron jobs.
- ac2u 4y ago>if you have a greenfield project, you should be using event-driven data processing. We got rid of the horse and buggy, let's please get rid of cron jobs. I don't see why event driven processing and cron-jobs (or any other time-based task scheduling mechanism), are strictly mutually exclusive.
- 0xbadcafebee 4y agoThey're not mutually exclusive. But the vast majority of tasks run by cron jobs are not time-sensitive.
- ac2u 4y agoExample of these jobs people are using for cron that are not time sensitive? Every shop I’ve worked in, events driven stuff might happen on producer consumer queue mechanism, whereas stuff that needs to happen at a certain time (ie, time sensitive) uses a scheduler/cron, or a idempotent scheduling system that’s consistently polled for things that should be happening “now”.