5 ms·
Not just a multi-cloud, but also managed kafka and a managed db across a multi-region deployment. Regions can fail, your job needs persistence and you need to m
by vaidhy 4y ago
Not just a multi-cloud, but also managed kafka and a managed db across a multi-region deployment. Regions can fail, your job needs persistence and you need to maintain the state of the message in the db..
oh!! have you also thought about the right queue semantics? Do you want your job to trigger exactly one, at least one or at most once? What happens if the previous job is still running when it is time to trigger it again? Is it 15 minutes from start to start or end of previous to start of next? How about metrics? Is your process idempotent?
So, the right answer is 42 unicorns.
- Crystalin 4y agonot so fast... young unicorns !! Where are you going to log the nasty errors when it fails. You probably want to setup a self-hosted cloud-based remotely-managed splunk and ensure someone does the maintenance/upgrade for you (those can be challenging) Have you properly setup your pager-duty ? I wouldn't want to miss one of the cron execution !!
- intelVISA 4y agoIt'd be literally impossible to deploy any of this lightweight, cloud-native architecture without at least 14 Terraform modules as well, maybe more (just to be safe).
- thesnide 4y agoI cannot unthink of It's the future (2015) https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/