And on 31st September . . .
I thought you pulled this service?
Well I scheduled it to be pulled!
Another long-in-the-tooth Azure service was put on notice this week. Azure Scheduler is (or, as of 30 September 2019, was) a service that did pretty much what it says on the tin. It fires off jobs through the likes of HTTP or HTTPS among others. Microsoft cited use cases such as pruning logs or performing backup tasks. The …
Is that you are less likely to need to change direction completely and for no apparent benefit to the customer.
If the new fangled way is better, why can’t they migrate the existing configuration automatically so that it doesn’t impact customers ?
We used to call this backwards compatibility, it wins big brownie points with management when we need to change things
Not at all surprised. The scheduler must have been to simple and reliable and dull. These days everything must have every feature under the sun and then some.
The further expand on the cron analogy. It too may see a similar push to the wayside by the systemd crowd. This is not isolated to Azure or Microsoft.
Why can't we follow the "if it ain't broke, don't fix it" mantra? Sure it may have a few issues, but they have been worked around. A simple modular system tends to work much better than a single complex gargantuan system.
No, we need to reinvent the wheel, and axle, and bearing, and drive linkage, and differential, and braking, and engine, and steering, and lighting, and chassis, and cab, ad nauseum just because we want to create a new car radio, then do it all again to add mp3 playing into the new, new car radio.
Get a professional automation suite, automate the hell out of your business and, if you really, really, really enjoy storing your crown jewels on somebody else's computer (the cloud), you can even run it there.
It is their business to keep forward and backward compatibility, and next to the basic stuff, you can integrate crazy stuff like ERP's, db's, as/400's, mvs (for the beardy guyz around) and a whole bunch of API's.
Fancy something like "run this every Friday except when Friday falls on a public holiday, in which case the process should run on Monday, except Good Friday, because there you want to run it on Thursday (Easter Monday ...)." ? Ensure that takes less than a minute to set up.
Note that CA have just bought up a lot of the competition and it is not quite clear which solution they will push forward and which they will put on maintenance (official term for customer-milking) mode, can hardly see them pushing them all, so, if you were to choose them, choose wisely, get assurances as to road maps and good bail out conditions if they fail to update regularly!
Biting the hand that feeds IT © 1998–2019