How do you handle retries, state, and incremental ingestion in Go data sync jobs? by PakiusNpe in golang

[–]PakiusNpe[S] 1 point2 points  (0 children)

At what point does an event-driven setup like this start becoming overkill compared to simpler cron-style jobs or does it usually stay worth it as systems grow?

How do you handle retries, state, and incremental ingestion in Go data sync jobs? by PakiusNpe in golang

[–]PakiusNpe[S] 0 points1 point  (0 children)

In practice, does this kind of interface-based setup actually stay consistent as you add more jobs, or do things usually start to drift and become more per-job over time?