Saturday, January 17, 2026
Cloud Native Now
MENU
MENU
Home
Webinars
Upcoming
Calendar View
On-Demand
Podcasts
Cloud Native Now Podcast
Techstrong.tv Podcast
Techstrong.tv - Twitch
About
Sponsor
MENU
MENU
News
Latest News
News Releases
Cloud-Native Development
Cloud-Native Platforms
Cloud-Native Networking
Cloud-Native Security
CPU and memory limits
Ten Common Kubernetes Misconfigurations That Cause Outages (And What You Can Do About It)
Learn the most common Kubernetes misconfigurations—like missing limits, probes, and AZ redundancy—and how to prevent outages in cloud-native systems ...
Andre Newman
|
October 21, 2025
|
Availability Zones
,
cloud-native infrastructure
,
cluster management
,
container orchestration
,
CPU and memory limits
,
CrashLoopBackOff
,
devops best practices
,
ImagePullBackOff
,
KubeCon 2025
,
kubernetes
,
Kubernetes misconfigurations
,
Kubernetes outages
,
Kubernetes reliability
,
Kubernetes troubleshooting
,
liveness probes
×
Exploring Trends in Mainframe Application Modernization
Step
1
of
8
12%
What is your organization’s primary approach to modernizing mainframe applications?
(Required)
Converting entire applications from traditional mainframe languages to a modern language such as Java
Selective modernization of specific modules or components
Building modular architecture from existing monolithic applications
Maintaining applications with improved documentation and understanding
We do not utilize mainframes at my organization
Does your organization currently have an application modernization initiative in place?
(Required)
Yes
No
Don't Know
What TWO factors MOST OFTEN drive your organization’s decisions to modernize specific mainframe modules? (Select up to 2 responses)
(Required)
High frequency of updates
Other
Cost reduction goals (MIPS, licensing, etc.)
Process optimization needs
Skills/talent gap concerns
Technical debt reduction
High frequency of maintenance
Changing business rules or requirements
What strategies does your organization use for mainframe code transformation?
(Required)
Maintain and document original mainframe code (COBOL, PL/I, Assembler, JCL, REXX)
Convert mainframe languages to Java or other modern languages
Refactor code into modular, reusable components
Maintain parallel versions (original and converted) for validation
Use AI-powered tools for code documentation and understanding
Use AI-powered tools for code conversion
Other
What is your organization's strategic direction for mainframe applications over the next 3-5 years?
(Required)
Mainframe-first: Keep applications on mainframe as a strategic platform, modernize in place
Cloud-first: Migrate applications from mainframe to cloud platforms
Fit-for-purpose hybrid: Place each workload on the most suitable platform (mainframe, cloud, or distributed)
Evaluating options / No defined strategy yet
Other
What factors MOST influence your organization's platform decisions for mainframe applications? (Select up to 2 responses)
(Required)
Security and compliance requirements
Performance and scalability requirements
Cost optimization
Skills availability and talent access
Integration with modern applications and APIs
Business continuity and risk management
Other
What are the TOP TWO benefits your organization expects from mainframe modernization? (Select up to 2 responses)
(Required)
Faster innovation and time-to-market
Better understanding of business logic and code documentation
Reduced costs (MIPS, maintenance, licensing)
Expanded talent pool and reduced skills gap
Improved system maintainability
Enhanced integration with modern systems
Other
How effective have AI-powered tools for code conversion been in your modernization efforts?
(Required)
Extremely effective
Very effective
Moderately effective
Slightly effective
Not at all effective
We do not use AI-powered tools
Δ
×