We use mainstream leading Open Source that drives the internet today. Robust with a huge user community
We will show you, how to automate your tests at the browser level; ideal for regression testing & releases to make sure all your modules are running properly
With our technology, you write your source code with simple POJO Java; your source codes are modular and more precise... you end up with fewer source components to manage
JtmCode: Building Modern Enterprise Applications: Inspired by the Mainframe Legacy
Developing complex enterprise applications can be a daunting task. The traditional approach requires a "full-stack" developer mastering various technologies, making them a scarce resource. Additionally, the complexities of frameworks like Vue.js, Angular.js, or React can add further challenges.
However, the enduring success of mainframe systems offers valuable lessons. Their secret lies in a core component: the middleware. This software layer sits between the operating system and application code, acting as a communication hub. It ensures reliable exchange of data between users, applications, and external systems. The middleware efficiently manages user sessions, handling input, context data, and output presentation.
Drawing inspiration from this robust and centralized approach, we can redefine how we build modern enterprise applications. This new approach will:
- Reduce development complexity by simplifying the application building process.
- Decrease reliance on scarce "full-stack" developers by enabling a more modular development approach.
- improve code maintainability and reusability through well-defined and centralized communication mechanisms.
- Enhance overall development efficiency streamlining workflows and leveraging specialized skills.
By learning from the past, we can build modern enterprise applications that are robust, scalable, easier to manage, and tailored to meet the specific needs of complex business environments.
By prioritizing simplicity throughout business application development, we ensure your modern application, like its mainframe predecessors, is built to endure for years to come.
Why JtmCode?
Modern Enterprise App Development: Move In, Not Build the House
Imagine building a new life, but instead of laying the foundation, framing the walls, and installing plumbing, you want to move in and start enjoying it. That's the philosophy behind our approach to modern enterprise applications.
Our foundational system software is akin to a pre-built, reliable house. We leverage the proven and enduring principles of mainframe architecture, ensuring its stability and longevity for decades to come.
This eliminates the need for you to spend time and resources on low-level development like writing core code and managing infrastructure. Instead, you can focus on what truly matters: building your business.
Think of it like this:
- Traditional approach: Like building a house from scratch, you'd need a team of specialists for various tasks – foundation, framing, plumbing, etc. This is time-consuming and requires extensive expertise.
- JtmCode approach: We provide the finished house, ready for you to move in. You just need a carpenter (Java programmer) to customize the interiors and add your personal touches - the functionalities specific to your business.
This streamlined approach offers several advantages:
- Faster development: Get your application up and running quickly, focusing on core business logic.
- Reduced costs: Eliminate the need for extensive upfront investment in infrastructure and low-level development.
- Simpler maintenance: Benefit from a robust and well-maintained foundation, minimizing ongoing maintenance hassles.
JtmCode empowers you to move in and start building your business, not wasting time laying the foundation.
Compare ( JtmCode vs Nonstop ) feature by feature
JtmCodedone_outlinedone_outline | HP Nonstop | IBM CICS | ||
---|---|---|---|---|
Error reporting | Standard Kubernetes / Docker to third party error capturing & reporting | EMS - Event Management System | ||
Context data Management for screen to screen data | Jtmcode Session management | Pathway's TCP (session management) | CICS | |
Defining/starting/management of processes | Kubernetes or Docker Swarm running Docker containers | Pathway's serverclass | CICS | |
Creating Screen Form and associated screen variables | JtmCompiler (Syntax check & produces EJS) | SCOBOL compiler (Syntax check & produces pobj) | MAP Compiler (MAP definitions) | |
Server class | Java server (Runs isolated in Docker container & context-free) | COBOL server (Runs standalone & context-free) | CICS region | |
Communication | Socket communication all provide by JtmCode | TELSERV (Socket communication for 6530 terminals) | CICS's BMS | |
Standards | Browser based - HTML5,CSS...latest use of modern technology! | Old 6530 terminal emulation | 3270 terminal emulation | |
Encryption | Browser based HTTPS (SSL encryption)...Latest Standard | Encryption of 6530 terminal data (uses third party) | ||
Load balance | Can run Application code in another server box, as volume grows | Load balance serverclasses to other Nonstop CPU(s) | CICS regions | |
Dynamic adding of new program server classes | Dynamic discovery when new backend server classes are added | In Pathway, add new serverclasses | CICS commands to install MAP and programs | |
Help pages | Help page per screen - can be slid in/out, built-in to every screen | Help page - usually a separate 6530 screen page | Help page - usually a separate 3270 screen page | |
Screen Languages | Switchable Multi-language support (ie. French & English)- even on the help pages | No Multi-language on 6530 terminals | No Multi-language on 3270 terminals | |
Realtime processing | add_circle_outline One of the hardest thing to build into code is exception and timeout handling, especially in situation where thousands of messages are flying back and forth | Pathway | CICS | |
Active-active configuration | add_circle_outline Kubernetes Or Docker swarm containers, running in an active-active configuration | Will be very expensive! | Will be very expensive! | |
OS Isolation from different versions | add_circle_outline Docker containers can isolate any system software upgrades; I.E. an OS upgrade to the host system will require regression testing, maybe code changes / recompiles; BUT by using Docker containers, the application program runs in its own version of the OS, which is part of the container and is therefore unaffected | Not possible | Not possible | |
New for 2021 February, Single Sign On (SSO) | add_circle_outline Allow user Logon Authenication using Open Id Connect (OIDC) standard. Farm out Logon to third party ie. Auth0 which handles all password authenication or 2FA or password recovery. With the additonal benefit of hacking detection and handling of 'Denial of service' (DOS) attacks. Once Authenicated, OIDC allows mulitple browser tabs to go directly to their first screen without logon again. | Not possible | Not possible |
What you can do with this platform and tools ?
- Create new applications using a browser with ease
- Migrate lagacy IBM CICS applications
- Migrate lagacy Tandem PATHWAY applications
Interesting Articles
- The Airline Industry’s Problem with Absolutely Ancient IT
- Brush up your COBOL: Why is a 60 year old language suddenly in demand?
- Long-Enduring COBOL May Still Have a Shelf Life
- Why, Where, and How JavaFX Makes Sense, by Björn Müller
- IRS details strategy for replacing its most ancient computer code
- What’s next for green screens?... , by Trevor Eddolls
- Mainframe Offloading and Replacement With Apache Kafka, by Kai Wähner
- Yes, You Can Migrate Your Mainframe to the CloudMainframe, by Mark Schwartz
- Mainframe Offloading and Replacement With Apache Kafka, by Kai Wähner
- OpenLegacy provides a way to quickly 'Open' your Mainframe thru API(s), so to off load to the cloud
- The Relevance of Mainframes in 2022: Eye-Opening Statistics
- Why major banks and financial institutions grow mainframe use