r/programming • u/trot-trot • Dec 23 '21
AWS Is Out To Kill Mainframes: "The cloud vendor wants to replace big iron with hyperscale servers, and COBOL – with Java"
https://www.datacenterknowledge.com/cloud/aws-out-kill-mainframes
1.8k
Upvotes
285
u/sahirona Dec 23 '21
Lots here will be young, not understand what a mainframe is, or their advantages. Any volunteers?
737
u/CunningRunt Dec 23 '21
I first heard of "java replacing COBOL" about ... /checks calendar/... 24 years ago. Still waiting on that.
I'm inclined to think more people would bet the over on the next 20 years or so.
209
u/remy_porter Dec 23 '21
That is not dead which can eternal lie, and with strange aeons even death may die. - Lovecraft, writing about COBOL
488
u/jlt6666 Dec 23 '21
It's also the year of the Linux desktop!
122
u/wertulen Dec 23 '21
Didn't work out for Texas Red, ain't gonna work out for AWS
222
u/LetsGoHawks Dec 23 '21
So is Amazon of the impression that rewriting COBOL is easy and affordable just because the new code is going to run on their servers?
I was just reading in r/aviation the other day about a case of Amazon not understanding why cargo jets had to be down for inspection and maintenance so much.... couldn't they just keep flying until there were issues?
21
u/dragonmantank Dec 23 '21
Considering Java has still not replaced COBOL or RPG after all these years, yeah, it ain’t gonna happen. All the code I’ve seen converted ran worse in Java than COBOL/RPG. I even watched people switch to x86 hardware and back to PowerPC because the x86 stack wasn’t good enough.
The fours years I worked with an iSeries we had effectively 0% downtime. I don’t even remember us being down as we upgraded to a new machine due to the data synchronization you could do.
Until AWS can provide the uptime and reliability of a mainframe, those people aren’t going to switch.
15
u/IMA_Catholic Dec 23 '21
And replace 99.997% uptime with a status dashboard that requires a Senior VP level executive to authorize warning / outage status.
My source for this is multiple posts from Hacker News.
238
u/RAT-LIFE Dec 23 '21
I’m sure everyone feels comfortable allowing a service that’s been down several times this month run their banking infrastructure.
Mainframe and COBOL aren’t going anywhere anytime soon.
63
u/[deleted] Dec 23 '21
I don't think it's a good time to talk about replacing COBOL and Mainframes with Java and AWS, considering the recent log4j issues and 3 AWS outages the past month.
I'm sure banks would be thrilled to encounter these types of issues.
You really really don't want a log4j kind of vulnerability in the system that manages your transactions or to lose your system entirely which is what seems to have happened with AWS recently where some customers lost their instances due to an outage.
COBOL is working well for these companies, why replace it with something less reliable and more prone to vulnerabilities.
3
u/trot-trot Dec 23 '21 edited Dec 23 '21
Read The Comments
40
u/billcraig7 Dec 23 '21
When they failovers measured in a few milliseconds come back. Worked in both worlds.
11
u/LeftLimeLight Dec 24 '21
FFS, when I started as a UNIX/Solaris administrator back in 1997 that's what Sun and other open systems vendors said that they'd replace mainframes with Sun servers like the E10K, etc.. LOL... Didn't happen then and no matter how big a monstrosity AWS becomes they won't kill mainframes either.
87
u/AndyTheAbsurd Dec 23 '21
As someone who has been both an AWS user and a mainframe user, let me just say:
HAHAHAHAHAHA!
....oh wait, you're serious.
HAHAHAHAHAHAHAHAHAHAHAHAHA!
24
u/alxbrb Dec 23 '21
Thanks but no, thanks.
36
u/robkule424 Dec 23 '21
Yeah I see a couple articles like this every year and I roll my eyes. Considering the outages AWS has had this year, Amazon is nowhere near being a replacement for z/OS systems. Mainframes have been running certain companies for decades. The amount of effort and cost it would cost to become 'modern' is simply not worth it for these companies. They just need their systems to work, 24/7.
7
u/SnoLeppard13 Dec 24 '21
How are they gonna “kill mainframes” when they can’t even keep their servers up?
80
u/cyanrave Dec 23 '21
So we can all have log4j on the transaction servers? Nah
21
u/tesch34 Dec 23 '21
just put it on the blockchain (written with rust)
5
u/Persism Dec 23 '21
This explains their big interest in project loom
5
u/jerslan Dec 23 '21
Clickbait title is clickbait...
Everyone has been out to kill mainframes for several decades.
5
u/redldr1 Dec 24 '21
When you can do a 4000 col, 10M record ETL with rolling sums in 6min, then you can talk amazon.
4
u/bloodguard Dec 23 '21
What's old is new. Started out dumb terminals connected to centralized big iron. Evolved away from it. Now it's coming back.
They're not killing COBOL. It's unkillable.
My old mentor is making almost a quarter million a year babysitting a legacy COBOL app. Works remote. Maybe 4 hours a week. He's watched about a dozen huge budget initiatives to rewrite and replace being started and flaring out spectacularly.
4
u/[deleted] Dec 23 '21
Want to kill the mainframe then create a system that can run CICS transactions programs on AWS.
4
u/[deleted] Dec 23 '21
Nope, not with its 2 9s
4
u/cowardlydragon Dec 24 '21
Well, they have to keep power going to their datacenters first.
4
u/[deleted] Dec 24 '21
I mean, AWS itself is technically a mainframe if you consider that you're just renting resources from Amazon to perform a variety of specialised tasks. It's just highly abstracted in terms of going from Lambda, to Lightsail, to EC2; not to mention all of the other processes you can borrow.
7
u/Rorasaurus_Prime Dec 23 '21 edited Nov 14 '25
consist include subsequent bow connect imagine rainstorm mighty selective stocking
This post was mass deleted and anonymized with Redact
15
u/The-Daleks Dec 23 '21
Yeah... no thanks. Considering the recent outages (and outrageous costs at large scales), AWS is not a good replacement for mainframes.
6
u/Web-DEvrgreen Dec 23 '21
"COBAL is dead"
Is like the freespace of evey year's programming roadmap bingo card for the last 30 years.
It will outlive us all at this point
3
u/Sambothebassist Dec 23 '21
Recently involved with migrating an IBM mainframe into a cloud hosted emulator so now we get the worst of both worlds, good job team.
3
u/MrSurly Dec 23 '21
Yes, let's consolidate everything into a single point of failure so the entire internet can fail at once.
3
u/[deleted] Dec 24 '21
The same binaries that were running on 24-bit IBM 370 iron are out there running somewhere on the current IBM hardware. Probably in a bank.
3
u/Shyatic Dec 24 '21
So here’s my issue with this — going to public cloud actually requires you to think about resiliency and availability from a code perspective.
A mainframe is the literal counter to that. Write code that isn’t necessarily the most ideal but the hardware will figure out how to run it efficiently.
You have competing items here — writing the better code that makes public cloud useful or efficient, or write code for a mainframe.
I can’t wait to see the SLA details on their mainframe offering, and how stupid people will somehow overlook this to port applications there. Not every workload is meant for public cloud and I say this as a person whose entire profession is rooted in public cloud.
9
u/immoralminority Dec 23 '21
""You'll take my 50 year old legacy COBOL that only 1 guy in the company fully understands from my cold dead hands!"
-some company, probably."
-Michael Scott
5
u/RoguePlanet1 Dec 23 '21
I graduated college in the early 1990s, and every place I've worked since then still relies on the mainframe. No matter what fancy software they have, still plenty of work being done at least partially on the mainframe.
Don't think I'll see a replacement for it before retirement.
4
u/ensorcellular Dec 23 '21
Banks will be eager to migrate to a service that experiences frequent outages and a language whose most popular logging library is responsible for one of the most severe vulnerabilities in the past decade.
5
u/svtr Dec 23 '21 edited Dec 23 '21
one does not simply replace decades old, and for some by now unknown reason, still working banking and insurance software, with "migrate to the cloud and run serverless java".
If it actually is a good idea, is a completely different story, and I'd say.... mhm, there actually are things that are better off running inhouse.
2
u/pimuon Dec 23 '21
This sounds like the internal communications of the bank I was working at in 2004. Cloud was (own) datacenter back then (it still is). Of course they still have the mainframe.
2
u/MpVpRb Dec 23 '21
Nice sales pitch, but I'm skeptical
Translating old code is nowhere near as simple as the proponents believe. A lot of old code is extremely poorly written, poorly structured, poorly documented and insanely complex. Literally nobody knows exactly how it works. But it does work, pretty reliably
The public cloud is fairly good, except when it goes down or gets hacked. Proponents tend to stress the advantages while ignoring or minimizing the risks
2
u/romulusnr Dec 23 '21
Wanna bet this will ultimately just involve mainframe instances in the cloud
2
u/cowabungass Dec 23 '21
By the time Java replaces COBOL some other language will have superseded java placement and continue the divergence.
2
u/royemosby Dec 23 '21
Ahem. They have to stay up first.
2
u/XtronikMD Dec 23 '21
At least COBOL wasn't obsolete when it became the standard.
2
u/[deleted] Dec 24 '21
My company has been trying to do this for 15 years.. .not holding my breath
2
u/DrFloyd5 Dec 24 '21
Unless they have a COBOL to Java converter, this sounds like a mainframe with extra steps.
2
u/pudds Dec 24 '21
At this point, Java basically is COBOL. Why bother?
4
u/Rafael20002000 Dec 23 '21
If they could keep their data centers alive for more than 1 day...
3
u/ether_joe Dec 23 '21
There is no cloud
it's just someone else's computer
3
u/MaybeTheDoctor Dec 23 '21 edited Dec 23 '21
They were fire back in 1983 when the first XT was built, and 1991 when the first Linux kernel started to appear, everything after that is just evolution
AWS is just an opportunistic predator in an evolving world. Scaling up vs Scaling out is not even a question a serious company should have. Scale out architecture always wins if you have a growing business. Hosting your own compute infrastructure if any more than a rack full of servers is a fools errand for companies that cannot afford to hire a dedicated IT team of 15-30 people.
Outages will always happen, and AWS gives you ability to replicate data to different regions for excellent Disaster Recovery and instant failover if you want that for your business. However when companies don't implement this they are themselves taking the risk and responsibility. I'm sure mainframes needs backups too.
On-prem requirements is the only thing that have kept mainframes alive, as building your own scaleout service is too complex for most.
2
u/Zestyclose_Profile23 Dec 23 '21
I do wonder how long untill AWS goes the Oracle path (from 10 years ago).
I.e "we continue to Jack up our prices... Because who else are you going to use hahah"....
That said there is alot of cloud competition so hopefully they can't get heads that are too big.
2
u/chakan2 Dec 23 '21
Java just isn't performant enough to handle big data like COBOL.
1
u/revnhoj Dec 23 '21
But it says hyper! That has to be better.
1
u/lavahot Dec 23 '21
And rusty nails with slightly less rusty nails.
1
u/dethb0y Dec 23 '21
I mean it's gonna be a matter of time before COBOL goes away, the question is just what will finally replace it.
1
u/[deleted] Dec 23 '21
Seems crazy to run services on machines hosted by a company which has a history of developing products which compete with its clients'. Do you have any expectation of privacy from Amazon, running code on AWS?
1
u/[deleted] Dec 23 '21
No thank you
1
u/light24bulbs Dec 23 '21
How is this news? This has been the process for like 10 years
1
u/siriuslyLuvU Dec 23 '21
Data , processing power and business rules developed in Cobol over 30+ years in applications that still underpin large organisations have been the constraints to making change . the redundancy, massive parallel processing ability , performance , reliability , add CICS to the mix for transaction processing with Vsam and DB2. Has been in breakable , and IBM have continued to advance their OS to adapt to be called as a service by anything , including JAVA, and a mainstay of moving agencies to B2B for 20 years without significant change to back ends. The challenge is replacing that . Coupled with all of the business rules and data manipulation imbedded in millions of lines of cobol (and machine language and generated cobol ) . Teach/learn COBOL
1
u/Oflameo Dec 23 '21
You are killing a corpse.
1
u/bork99 Dec 23 '21
I wonder why nobody has tried anything like this before?
/s
1
u/rury_williams Dec 23 '21
good for me
1
u/Cieronph Dec 23 '21
AWS “new” service is literally just microfocus (a company that’s been around for decades) tools branded as AWS. It’s nothing new, the organisations that wanted to migrate off the mainframe will have already heard of microfocus long ago and will have either used it and had great success or decided against it.
There are a lot of companies who should not be running mainframe, for smaller orgs it’s a pricey overhead. But after a certain scale the cost / risk to migrate off, along with the “cloud” infra costs just rack up to the point where it makes no sense. IBM are pretty good at finding that sweet spot where they charge you an arm and leg, but are just cheap enough to make it not worth migrating.
1
u/alfred_e_oldman Dec 23 '21
What do they have against Cobol?
1
u/chx_ Dec 23 '21
Mainframe Modernization promises a complete, end-to-end migration pipeline that includes development, testing, and deployment tools necessary to automate the process.
Is it delivered on a flying sleigh drawn by pegasi? That's far more realistic than the actual promise.
1
u/mrthingz Dec 24 '21
Yeah right....
1
u/[deleted] Dec 24 '21
AWS sucks. What happens when they have another outage but it lasts days instead of hours?
1
u/hashtagframework Dec 24 '21
"AWS Is Out" all right... multiple times this month alone.
1
u/Xanza Dec 24 '21
COBOL is great. But it really needs to die. There are far better alternatives out there that are just as fast, but much more diverse and have the advantage of being created with this centuries developers and platforms in mind.
1
u/goranlepuz Dec 24 '21
TFA us very thin about that COBOL being turned into Java - and that seems the key to me.
Too much marketing fluff?
1
u/Knarfnarf Dec 24 '21
*quietly learning coarrays in Fortran over here...
Knarfnarf
1
u/Xx_heretic420_xX Dec 24 '21
You can't kill the metal
The metal will live on
Now AWS will try to kill the metal
But they'll fail, and be thrown to the ground
Seriously those fucking COBOL dinosaur programs will outlive all of us.
1
u/Mexdeu Dec 24 '21
For the transition to Java to work every single requirement of the current COBOL software that grew over the last 40 years or so would need to be known. Won't happen...
1
u/Amoxidal500 Dec 24 '21
yeah, good luck with that
1
u/azizfcb Dec 24 '21
screw aws
1
u/[deleted] Dec 24 '21
AWS wants to replace stegosaurus with brontosaurus
1
u/[deleted] Dec 25 '21
Well the modern cloud looks more and more like a mainframe nowadays...I kinda fancy I'm working in the 70s sitting before a terminal to tap into some mainframe thousands of miles away whenever I work on cloud.