Last Update: 16.10.2018. By Jens in Newsletter
This unnecessary server and cronjob of yesterdays mail was only the tip of the iceberg. It got worse as I had to run the scripts manually to trigger an import.
The whole import process should only go as:
fetch the CSV from remote -> import it on preprod -> if success import it on prod
The import steps have a few sub-steps but they don’t matter here and are still pretty small in scope.
However, that little process spans over two command line apps with 6 cronjobs on three different servers and some behind the scenes filesystem-copy-magic. I won’t bore you with the details but even when we kill the in-between server, it is still two command line apps, 5 cronjobs, and two servers… For a tiny import in a tiny application. There is nothing complex behind it. No fancy logic, no nothing.
One of the apps is doing the actual import and the other is some workflow wrapper; copying files, sending emails, etc. The funny thing is, this workflow wrapper app never ever calls the actual import app. Their interaction is done via cronjob scheduling :-)
Keep it simple.
That mess is not simple. Don’t build such a mess.
Want content like this in your inbox
each workday irregularly? No BS, spam or tricks... just useful content: