Mont Blanc is [not] the highest mountain — risks of local optimization
The best solution may not be the best solution. Depending on the scope in which you consider the alternatives, you may arrive at the wrong conclusion. Consider only the problem at hand, there may be an apparently easy solution that in the grander scheme of things is not optimal and perhaps even detrimental. Accepting that you do not decide the scope to apply and are forced to work in a scope much larger than you can oversee can be quite hard. Agreeing to objectives, constraints, decisions that fit in with that larger scope — but seem conflicting with the one you thought to be dealing with — can be difficult and frustrating. Yet, you may have to submit — just as you pay taxes and follow traffic rules.
This may all sound a little abstract. Let me give you an example. The team of database specialists I work with is busy with planning a few major steps for the existing applications & platform. From over a 1000 local instances — database, applications, integration platform, low code platform — we are moving to a small number of central, consolidated and cloud based instances. A major move. Part of this landscape is a substantial number of scheduled jobs that run throughout the day. Most jobs do database intensive work and a large number runs only stored procedures inside the database platform. The scheduling currently is done…
