Sorry for being vague, but that was on purpose. I wanted to see what opinions and recommendations there were for event-driven process versus cron.

Seems cron looks like it may be the way to go after all for both maintainability and performance. I just was not sure that starting a process every 3-5 minutes would be the best use of resources.

But, to the specifics, I need to do the following:

  • check a folder for files and process each item in there with a script, period: 5 minutes
  • check a REST API for new items and process them with a script, period: 15 minutes
  • check a REST API for changes in existing items, period: 24 hours
  • check to see whether services are running and email alert if not, period: 5 minutes
  • check for new uploads for a folder and move them to the processing folder above, period: 1 hour
  • compress/archive uploaded JSON/log files, period: 24 hours

    The last item seems more like a monitoring system like nagios, zabbix, etc. but it is only 4 nodes and one tcp service port so easy enough to do on my own.

    Thanks for all of the feedback so far.

    In reply to Re: Long-running automation tasks by bfdi533
    in thread Long-running automation tasks by bfdi533

    Title:
    Use:  <p> text here (a paragraph) </p>
    and:  <code> code here </code>
    to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.