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.
Many IT budgets are consumed by maintaining existing applications and resources, and getting out from under the weight of these existing applications can be daunting—schedule is king, and making time to address modernization comes at the expense of current business needs. However, as the business world moves into the digital space to prepare to meet the next generation of customers and to compete globally, organizations can’t manage their applications in the same way as they have in the past—they must take them to the next level.
Cloud technologies provide many of the building blocks to help businesses achieve these goals and prepare themselves for the future. This white paper is a solution-agnostic resource to help you understand enterprise cloud modernization and migration and to help you decide which strategy is right for your business. Are your applications ready for the new tomorrow?
We are excited to announce Keyhole Software’s partnership with Microsoft to sponsor Azure App Modernization and Innovation Day on April 15, 2020.
During this free community event, attendees will have the opportunity to learn about Azure developer services and the latest on industry trends from Azure application development experts.
The agenda for the day will include three presentations with topics such as Azure App Services, Serverless Computing, Microservices & Containers, DevOps on Azure, AI for Developers and more!
One of my most recent projects involved helping a client move many decades of code from a mainframe environment to a distributed Java web environment. The client had engaged another company to actually transform the mainframe code to Java, and our team was tasked with making it all actually work.
One of the major areas we had to deal with was the transition of all of the batch processes. Of course, Spring Batch came to our rescue for most of the work, and was an easy choice as we were already using Spring Boot to wrapper the converted applications.
The most challenging part of the entire project was that the client did not want to move everything at once in a Big Bang, but rather a few programs as a time. This meant that some programs would be running in the Java environment while others remained on the mainframe.
In this blog, I discuss three data challenges we encountered in the transition of an enterprise mainframe to Java web application with Spring Batch, how we overcame them, and tips to keep in mind going forward when in similar migration situations.
- Page 1 of 2