Mainframes have long powered critical financial transactions and government operations. However, across the U.S., particularly in Kansas, these systems are showing their age. The COVID-19 pandemic exposed a critical issue: essential services like unemployment insurance were crippled by outdated COBOL systems, causing significant delays. This is more than an inconvenience; it’s a clear signal that mainframe modernization is urgently needed …
The Keyhole team is proud to announce the publishing of a new, free white paper: COBOL Modernization Strategy with Spring Batch
This strategy positions Spring Batch as an irresistible proposition for organizations ready to bid farewell to their COBOL legacy. Keyhole Software offers guiding principles for COBOL modernization, with a comprehensive guide based on tangible experience for enterprises navigating the realm of COBOL modernization.
In today’s rapidly evolving digital landscape, cloud computing stands as a beacon of innovation and efficiency. However, the journey to the cloud is often marked by a series of complex challenges. Understanding and addressing the common cloud migration challenges & how you address them is critical for businesses seeking to harness the full potential of cloud technology. Importance of Security …
In this blog post, I will demonstrate a technique to query the status of a SQL Server Agent job that executes the SSIS package. SQL Server Agent scripts are asynchronous in nature. This can make it difficult to make code decisions based on the execution status of a script of this type.
This blog is about converting legacy code better—using architecture already in place, SOLID principles, and best practices.
Generally speaking, not having an architectural plan set up (or not using SOLID principles and best practices) can lead to passing the buck to the next generation of developers. We should all strive to push good code forward to get the latest and greatest out there. Starting with following the patterns in place at your job, or SOLID best practices, will make converting and upkeep way faster in the future.
This post contains a discussion of my experience in various software team environments. Throughout them all, we show that if SOLID patterns and best practices had been followed, then time spent converting code would have been less and code upkeep would have been easier down the line.
