Define a multithreading threshold when building SaaS applications
Encounter multithreading challenges when interfacing COBOL and Java in a SaaS app
From the developerWorks archives
Date archived: May 14, 2019 | First published: April 18, 2013
While on-premise COBOL programs have been successfully transformed into Java™-based Software as a Service (SaaS) applications, there are multithreading issues developers should watch out for when interfacing COBOL and Java with one another in a SaaS application. The author illustrates what proactive actions to take in a multithreaded SaaS failure scenario.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.