I am looking to connect with any peers that have migrated their mainframe to the cloud or looking to do so. What have your experiences been and what advice do you have about the process?

Data CenterMigration
1.6k viewscircle icon3 Comments
Sort by:
Director in Manufacturing2 months ago

The application purpose and value to users might push you in different directions. We had proprietary Fortran code running on our IBM 390 in the 1990’s to around 2009. We ported the code to Solaris, which didn’t work out too well and then did a rewrite of the application to Red Hat Linux. Due to the proprietary nature of the code we aren’t going to the cloud but who knows, decisions change all the time

What can you folder to your community? Faster execution? New features? Better interface? Start there

1 Reply
no title2 months ago

Some day we can edit posts… what can you offer your community…

Senior Director of IT in Construction2 months ago

I think the approach depends on the objective and desired outcome; whether it's a re-host with minimal changes (lift-and-shift), refactor with some changes for cloud efficiency, re-architect to break up monolithic application(s) to  microservices or containerization, or replacement to cloud Saas solutions.

Content you might like

Which tool do you use for task automation at your work? Comment if you use other tool.

Zpaier16%

Make (Formerly Integeromat)35%

IFTTT19%

Other tool22%

I like to learn task automation2%

No task automation3%

View Results

Do folks think the impact of the social media addiction cases in the state court JCCP and MDL N.D. California will be far and wide, seeping into insurance industry changes as well as technological, or will Section 230 save the day once more for platforms?

The case will settle; zero to minimal impact70%

Yes! But effects and repercussions are unknown30%

Our organization is implementing an Internal Developer Platform (IDP) to enable self-service infrastructure provisioning, and we're evaluating Terraform Cloud workspace management strategies.  We're debating between: - VCS-driven approach: Repository-based workspace management with GitOps workflows - API-driven approach: Programmatic workspace creation and management via Terraform Cloud APIs Specific Questions: - Which approach have you found more effective for true self-service at scale? - How do these approaches handle multi-tenancy and isolation requirements? - What integration challenges did you encounter with developer portals/service catalogs? - How did your choice impact developer adoption and platform team operational overhead? Would love to hear about your real-world experiences, particularly around the trade-offs you discovered post-implementation.

We are wondering if other companies that are hosted on the Cloud (AZURE/GCP or AWS) have implemented File Integrity Monitoring solution on Openshift? Would you have a return on experience?

Has anyone used Denodo to create an abstraction layer that contains semantic models driven by federated queries?  If so, what has your experience been related to performance? Cost?