4 ms·

There is no way you can do that reliably without a K8S multi-cloud cluster.

by POPOSYS 4y ago

atraac 4y ago
At this point I don't even know if this comment is satire or not.
- Sirened 4y ago
  I don't see how it's satirical. If you need a job to run, you need to handle the case of transient node failures. K8S helps alleviate this issue by allowing the job to be launched on any of a choice of nodes. Sure, cron is fine if you're just looking to rotate logs on the local machine, but if you want to reset your nuclear watchdog timer, you may want something more reliable :)
  - actionfromafar 4y ago
    If you need a job to run, you need to handle the case of governments turning against you. A huge nuclear capable military and a top notch spy agency helps alleviate this issue by allowing missiles to be launched on any belligerent nations.
    - oxfordmale 4y ago
      I best add a nuclear capable military to the 2023 budget. I know we need to look after every penny, however, the increased reliability is surely worth it.
      - SahAssar 4y ago
        Just use AWS MAD.
  - cedws 4y ago
    I'm sensing a need for a blockchain here.
    - ashwagary 4y ago
      These replies made my day. Thanks guys.
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 ago
  not 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 ago
  It'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 ago
    I cannot unthink of It's the future (2015) https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/

There is no way you can do that reliably without a K8S multi-cloud cluster.

atraac 4y ago

At this point I don't even know if this comment is satire or not.

Sirened 4y ago
I don't see how it's satirical. If you need a job to run, you need to handle the case of transient node failures. K8S helps alleviate this issue by allowing the job to be launched on any of a choice of nodes. Sure, cron is fine if you're just looking to rotate logs on the local machine, but if you want to reset your nuclear watchdog timer, you may want something more reliable :)
- actionfromafar 4y ago
  If you need a job to run, you need to handle the case of governments turning against you. A huge nuclear capable military and a top notch spy agency helps alleviate this issue by allowing missiles to be launched on any belligerent nations.
  - oxfordmale 4y ago
    I best add a nuclear capable military to the 2023 budget. I know we need to look after every penny, however, the increased reliability is surely worth it.
    - SahAssar 4y ago
      Just use AWS MAD.
- cedws 4y ago
  I'm sensing a need for a blockchain here.
  - ashwagary 4y ago
    These replies made my day. Thanks guys.

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 ago
not 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 ago
It'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 ago
  I cannot unthink of It's the future (2015) https://circleci.com/blog/its-the-future/ https://circleci.com/blog/its-the-future/