3 ms·
Interesting demo. The GitHub here and the demo (need LinkedIn account?) is in linked discussion by https://www.linkedin.com/in/garycrook https://www.linkedin.c
by ngcc_hk 4y ago
Interesting demo. The GitHub here and the demo (need LinkedIn account?) is in linked discussion by https://www.linkedin.com/in/garycrook https://www.linkedin.com/in/garycrook
“Last week, Amazon Web Services (AWS) published their IBM #Mainframe Card application as open-source.
In 3 HOURS, using Heirloom®, we deployed it to 3 different cloud platforms - AWS Elastic Beanstalk, Google Cloud App Engine, and Microsoft Cloud Azure App Service. All 3 provide cloud-native infrastructure for resiliency and dynamic scaling. No additional vendor proprietary software needed - literally plug & play.
Hour 1 - pull from the repo, organize the project workspace, and transpile the application code into a single Java application package (.war). ~35K LOC processed in < 3 seconds, zero changes to the application code, zero errors.
Hour 2 - migration of VSAM data into target relational cloud database - an RDS PostgreSQL instance on AWS.
Hour 3 - application configuration and deployment to the 3 cloud platforms (using exactly the same Java package on each).
With provisioned infrastructure and configuration complete, the entire process can be automated using a CI/CD pipeline, migrating the application to the cloud in just a few minutes.
#agilityMatters #humbleBrag #mainframeMigration #mainframeModernization #COBOL #PL1 #cloudAgnostic #multiCloud” and a video posted by him under LinkedIn.
- ngcc_hk 4y agoFound out he is microfocus hence partially he will know but partially not sure. Busy on other things and hence not fact check. But not likely fake.
- shrubble 4y agoPorting a language designed to be portable and ETL-ing the data is the least of the issues. I would think that there are many other considerations for a mainframe application, such as security, predictability, data integrity etc.