Last week, I wrote about how middleware came about because of the emergence of distributed computing systems. I wrote that these new systems created a need for certain types of software that had not existed before or existed mainly for internal use. Middleware software has roots in software that was developed for centralized computing for both batch and online processing. This week I focus on the real-time roots of modern middleware.
Read More
Posted: November 07, 2016 |
It’s generally accepted that modern middleware came about because of the emergence of distributed computing systems. These new systems created a need for certain types of software that hadn’t existed before or existed mainly for internal use. This new software came about to support client-server computing. However, modern middleware software has firm roots in software that was developed for centralized computing.
Read More
Posted: October 31, 2016 |
This week, I am continuing this series on significance (the quality of being worthy of attention or importance). For this post, I want to focus on z/OS, an OS that’s been used for more that 15 years and has it roots in predecessors from OS/390, MVS/ESA, MVS/SP, OS/VS 2, OS/VS1 and OS/360 (which first shipped in 1965). z/OS has been more than 50 years in the making with a huge investment of human computing resources and large and varied input from its users over the decades.
Read More
Posted: October 24, 2016 |
This week, I am continuing this series on significance (the quality of being worthy of attention or importance). For this post, I want to focus on virtualization.
Read More
Posted: October 17, 2016 |
This week, I am starting a new series on significance (the quality of being worthy of attention, importance). For the first in this new series, COBOL is my starting place.
Read More
Posted: October 10, 2016 |
This week, I’ll finish my exploration of IT modernization by writing about CICS and IMS Transaction Manager (TM). Both are powerful transaction environments with a long history of internal modernization. However, more than their history is their pursuit of powerful functionality, high performance and innovation.
Read More
Posted: October 03, 2016 |
This week, I’ll explore internal modernization by writing about change and growth that has happened to DB2 and IMS database (DB). When you read the different accounts of the history of these products, you can’t help but think of the number of individuals and teams involved and the dynamics and energy of their interactions. There are the development teams. They designed the initial functionality, then all the follow-on developments were taking place over decades while technology was constantly changing in and around them.
Read More
Posted: September 26, 2016 |
This week, I’ll explore the idea of internal modernization by writing about change and growth that has transformed legacy languages and files systems. Some modernization proponents say, “dump COBOL,” but are you aware of the internal modernization that has happened within COBOL over the decades? It’s an amazing story described in dozens of books written about COBOL over the decades.
Read More
Posted: September 19, 2016 |
This week, I’ll explore modernizing the way applications are created and supported through change management. Existing applications were created in one way—is this the way modernized applications should be changes and sustained in the future?
Read More
Posted: September 12, 2016 |
This week, I’ll focus on modernization by exploring replacing some or all of the files for an application with a database solution. Let’s see if and when this is a compelling idea.
Read More
Posted: September 05, 2016 |
