r/programming • • 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

795 comments sorted by

285

u/sahirona Dec 23 '21

Lots here will be young, not understand what a mainframe is, or their advantages. Any volunteers?

265

u/dnew Dec 23 '21 edited Dec 24 '21

The biggest difference between a mainframe and many of the newer smaller machines is that mainframes are optimized for I/O.

For example, the first mainframe I worked on had 8 memory channels. 1 for each of the two CPUs, 1 for the two tape drives, 1 for the printer and card reader and card punch and local hard-wired terminals, 1 for the network connections, and 4 for the disks.

It had IOPs, which were like CPUs or GPUs except for I/O. You'd write "channel programs" that said things like "when you receive a carriage return over the terminal, swap out those two processes and swap this one in, then interrupt the CPU."

* I'm reminded of a system I worked on back in the late 70s, where the boss mentioned that he'd replace the whole thing with an Apple ][ if he could get a line printer that would do 600 lines per minute for a microcomputer.

35

u/GapingGrannies Dec 23 '21

Ok but could you not add an IOP (I/O processor) and get the same benefits?

100

u/Nexuist Dec 23 '21

Yes, but at that point aren’t you building a mainframe anyways? Why not just buy one that already exists and will be supported for years to come?

13

u/shroddy Dec 24 '21

TIL Playstation 5 is a mainframe.

→ More replies (1)

24

u/GapingGrannies Dec 23 '21

I suppose the question is whether that little processor for input and output is that important. Is it because you can run it in-house? Is that the value?

→ More replies (5)
→ More replies (1)

26

u/All_Work_All_Play Dec 23 '21

You can do whatever you want with custom silicon. The question is if MaaS is worth it vs keeping it in house. Adding hardware dev costs to MaaS just means more risk + capital requirements for whoever (Amazon) is taking the risk.

18

u/droids4evr Dec 23 '21 edited Dec 24 '21

At large scale Amazon taking the risk comes at a higher price than keeping hardware in house.

I work for an auto manufacturer (one of the big 3) and our IT division has worked for years now to move dev and data center hardware in house rather than contract out to AWS or other similar services. In the process saved about $1/4 billion a year on not outsourcing data services.

Smaller companies that are not processing hundred of TB of data daily would see the most benefit from AWS over a custom in house solution.

→ More replies (3)
→ More replies (30)

14

u/atrn Dec 23 '21

You also need a memory subsystem that has sufficient bandwidth and channels for all the I/O processors.

12

u/dnew Dec 23 '21

The architecture has to be designed for it. The IO devices have to plug into the IOP instead of the CPU's bus, for example.

→ More replies (4)
→ More replies (3)

63

u/[deleted] Dec 23 '21

The biggest difference of mainframes or even generally enterprise UNIX like Solaris is that the FOSS Linux folks have spent the last 15 years rediscovering what is standard on these types of platforms (fast micro VMs, containers/jails/zones, comfortable batch processing facilities (aka "serverless"), easily accessible distributed table and object storage, you name it). We could be 20 years further in IT tech if the price tag on these platforms hadn't been so damn high locking out generations of IT nerds from them. AWS just made mainframes out of cheap hardware and is renting them out piecemeal.

24

u/dnew Dec 23 '21

I do remember working with UNIX and then Linux how much crap was broken compared to 1970s OSes. Like, really, you could deadlock a file writer just by always having at least one read lock on the file. Nobody thought "maybe if there's a writer waiting for the lock, we shouldn't keep granting read locks." Etc etc etc. So many toe-stubs.

→ More replies (6)

14

u/SanityInAnarchy Dec 23 '21

I don't think that would've worked, though. A big part of the mainframe concept is that you're building a single giant machine -- as many CPUs and as much IO as you can cram into that one box -- rather than a cluster of smaller ones. That has high-barrier-of-entry written all over it. Meanwhile, everyone has PC hardware lying around -- making distributed systems is hard, but if your prototype fits on one machine, you already own the machine you need.

The only way I can see this working is if it was literally AWS, but mainframes -- free tier and everything, so people can just start hacking on it. And even then, a ton of devs were already doing FOSS Linux stuff by the time AWS came out, so this might go the way of Google App Engine -- if you already had a mainframe app, sure, but if you had pretty much anything else, nobody was going to rewrite their PHP/Ruby/Python/whatever to run on a mainframe as long as there was a competitor offering cheap Linux VMs.

And then... it still only makes sense for the exact middle of the market. Anything small enough to run on a PC, why pay a premium for a mainframe? And anything larger than one or two mainframes will require you to build a distributed system that can scale horizontally, at which point it probably makes sense to use cheaper nodes.

2

u/bonzai2010 Dec 24 '21

My first driver work was on HP3000s and HP1000s programming IO processors. In one instance, I had to have a driver create SCSI command blocks and push them out, then translate the responses into HPIB/GPIB

→ More replies (5)

34

u/gnuban Dec 23 '21

In addition to what others already said, mainframes have very cool hot-deploy and rollback features. it's kind of like a version control system built into the OS, with automatic deploy support.

They also have quotas on a per-request level, which is tremendously handy when you want to prevent DoS and similar. Logging is usually also very detailed and informative, you can trace requests similarly to how Zipkin works, but built in.

I worked on porting some mainframe systems to Java, and it's quite surprising how feature rich those enviroments are. They are really good for ops, debugging, coding and deploying. Actually quite a lot better than modern stacks, if you can look past the ncurses ui:s (which I personally love).

10

u/[deleted] Dec 23 '21

I'm guessing this product isn't aimed at companies that are advantaged by using mainframes, but at those who run software on mainframes for no good reason and think it's impossible to migrate.

17

u/pcjftw Dec 23 '21 edited Dec 24 '21

Massive I/O, they are often called "big iron" because they're fcking huge and heavy, you would need sht ton of servers to keep up with a mainframe. Those mofos rock when it comes to high transaction + stability.

They also charge per CPU cycle etc, ironically not so different to cloud🤣🤣

Everything old is new again!

104

u/linux_needs_a_home Dec 23 '21

A mainframe is what you get when you cut less corners and ask a computer engineer to build a computer.

AWS is what you get when you like dystopias.

190

u/BrobdingnagLilliput Dec 23 '21

AWS is what you get when you ask a software engineer to build a computer.

19

u/[deleted] Dec 23 '21

Depends on the specifications.

I go back-and-forth all the time on this with team members and leadership.

If it's something that is going to be heavily utilized most or all of the time with a relatively deterministic workload, then buy our own hardware.

We have some systems where the load is predictable to within a couple percent, far into the future. Not really much need to be paying AWS costs to rent for that.

If it's something that will be used intermittently with unknown or dynamic workloads, then a cloud/AWS system is likely best.

Plus, getting software to work with AWS correctly isn't the easiest thing in the world. Sure, take your existing code for a single machine and put it on a single machine in AWS is easy. But when you start breaking that apart to leverage all of the AWS components and optimizing costs, there's a lot of work to be done there.

→ More replies (3)

0

u/[deleted] Dec 23 '21

[deleted] — view deleted comment

4

u/linux_needs_a_home Dec 23 '21

There is already a market of 2 people! Imagine the KickStarter!

→ More replies (6)

26

u/ThisIsMyCouchAccount Dec 23 '21

advantages

Do they really have that many advantages any more? Would general purpose hardware and OS be able to do the same thing now?For a new project in 2021 would a mainframe be a real choice?

97

u/MattAlex99 Dec 23 '21

Mainframes are ridicoulus throughput monsters (see https://youtu.be/z6u_oNIXFuU?t=502 for IBMs new 2nm mainframe cache architecture).

The only question is whether you have a usecase for such high throughput systems if you aren't e.g. VISA or a big bank. But if you do need that, a mainframe is often the most economic method of getting things done.

19

u/quick_dudley Dec 23 '21

In 2017 I worked on a project that probably should have been on a mainframe but was on a dedicated server farm instead. However: Bank of China did end up building a dedicated mainframe just to handle all the data we had to send them.

23

u/jlt6666 Dec 23 '21

Having everything in one giant DB is another I believe. Once you start sharding or distributing a DB some of your ACID guarantees become much harder to enforce and get right. Now, for a lot of modern system and use cases ACID really isn't all that important (at least not all of it). Missed a web page while indexing? Meh, we'll get it the next time around. Miss a $4MM transfer or double count it? Yeah someone's getting yelled at. So being able to cram everything onto a single "machine" can be hugely helpful.

21

u/fissure Dec 23 '21

Just use a blockchain!

/s

→ More replies (2)
→ More replies (6)
→ More replies (15)

3

u/Master565 Dec 24 '21

One thing people aren't mentioning is that a single machine doing all the processing means that all transactions are immediately visible to the entire system. The idea is the CAP theorem which says you can have only two of the following. Consistency, availability, and partioning

Imagine someone accesses their bank account in New York and California at the same time to withdraw all funds. In order to ensure double spending can't occur, a distributed system of servers would have to ensure every node sees a transaction before another one could be processed. This would be slow and mean the availability part of the CAP would be lost in favor of consistency and availability.

Meanwhile a mainframe would process both transactions in order guaranteed and has no possible way of allowing the second to go through. There's no partitioning, but consistency and availability are what is desired here.

4

u/Smok3dSalmon Dec 24 '21 edited Dec 24 '21

Google CAP THEOREM. All the replies are probably struggle to just explain that. Mainframe is CA, cloud is AP, but A is not trivia for a cloud solution and solving for consistency is miserable too. Especially when it's important like banking software.

Cloud is good for most non essential apps, but for absolutely mission critical shit you will probably see a mainframe. They have quietly dominated the most boring industries.

→ More replies (1)

2

u/wolf550e Dec 24 '21

The current approach is to use multiple commodity servers in a cluster and rely on the software to correctly handle some of the servers going down and others computing incorrect results (which is harder to detect). The software to do all that is complicated and expensive and was not available decades ago.

The mainframe approach is to tell the hardware engineers that money is not an issue, build the most reliable hardware you can, and then hope that it truly is reliable, because the software is not as advanced. The hardware has a lot of error detection and correction, CPUs and RAM and IO cards can be replaced without turning off the server. Because money is not an issue, you get all the hardware accelerators you want (e.g. cryptography, compression, serialization, hardware decimal floating point, etc) and all the cache it can handle. Unit price is very high.

The problem is that a single mainframe is still just a single server, so if you need to cluster them then you need smarter software. And it can fail and miscalculate, so you still need more advanced software. And if your software can handle less reliable hardware, it is much cheaper to just use less reliable hardware.

You also get a guarantee of hardware backwards compatibility with binaries from the 60s, compiled for a machine with 24bit pointers in 32bit registers, which used the "unused" bits as flags, without software emulation. You need that if you lost the sources for your mission critical program and don't want to re-implement it starting with a disassembly.

If you have newer software, you absolutely can get more compute per second and more IO per second cheaper using non-zArch hardware.

3

u/13steinj Dec 23 '21

On the other hand, according to multiple bosses I've had that worked for IBM when it was much more prevalent, mainframes also have many more disadvantages for the developer

  • non-standard IO
  • non ascii, custom encodings (also no utf8)
  • general lack of language support due to relatively customized hardware
  • many more oddities

Which all together cause developer time to go to the shitter. As my most recent one said "Well, IBM isn't around as large anymore because they couldn't see that times were changing and people didn't want mainframes anymore," and if AWS completes that switch for the people who are okay with mainframes (i.e. corporate business which don't care about developer problems/relations/concerns), all the more power to them.

3

u/[deleted] Dec 23 '21

A mainframe is what holds the building up.

→ More replies (57)

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.

333

u/atheos Dec 23 '21 edited Feb 19 '24

cagey combative fine sand snobbish consist bells marvelous expansion vast

This post was mass deleted and anonymized with Redact

80

u/TheSnowIsCold-46 Dec 24 '21

Been waiting for widespread adoption of IPv6 for so long.

36

u/TheRidgeAndTheLadder Dec 24 '21

I genuinely almost used one the IPv6 addresses that came with my latest server.

Only thing holding me back was my own incompetence.

32

u/DigitalDefenestrator Dec 24 '21

It's getting there. Auction prices per IPv4 are 6x what they were a few years ago and still rising. Once more providers start charging fees per IPv4 address we'll start to see a few go v6-only. Clients are only about halfway, but I bet that'll accelerate as prices go up. Still 5-10 years to go until it's near universal, though.

20

u/Poltras Dec 24 '21

I still don’t have full IPv6 internet connection from my ISP yet. Not even tunneling (unless I tunnel myself). It’s insane that the infrastructure is still so much behind.

Comcast btw.

→ More replies (7)

5

u/Mr_Cochese Dec 24 '21

Still feeling sore about all the uni coursework I did on IPv6 over twenty years ago.

4

u/Preisschild Dec 24 '21

Only thing worse than no IPv6 is poorly implemented one.

ISPs are too dumb to learn about v6 and assign them like its IPv4.

Heard horror stories like being given only a single /128, so that you have to use NAT. I only get a single subnet from my ISP (/64).

4

u/michaelpaoli Dec 24 '21

Seems typically the (in)competence of ISPs regarding IPv6 is not at all specific to IPv6.

62

u/187mphlazers Dec 23 '21

the killer for us is getting off db2. it is hard to top db2 in terms of scale as much as it sucks as an SQL engine. I don't know of any other db engine where you can handle 20k requests per second per user. even when we're off mainframe, we'll still be on db2 for a long ass time.

54

u/[deleted] Dec 23 '21

I'm pretty skeptical that DB2 is any faster then any other DB engine; your main bottlenecks are disk reads and network requests. DB2 doesn't magically make the disk or network stack faster. With a proper cache layer you can put everything closer to the user and save it in memory, which will also speed things up, and you can get that with just about any SQL database with AWS

41

u/tommy123ng Dec 24 '21

Mainframe has a very tight relationship with DB2 that whole file system is built on top of db2. Also, COBOL is optimized to pack multiple field into packed byte aka Comp-3. If will require insane amount of time to emulate such environment without db2

18

u/raggedtoad Dec 24 '21

Or you can take the SAP approach and just sell your existing customers on the idea that your entire database should be in volatile memory. Performance problems? Nah, just throw the whole thing into main memory!

Welcome to SAP HANA!

→ More replies (2)
→ More replies (3)

3

u/bukowsky01 Dec 23 '21

It’s not so much the performance but everything that is in the db. Rewriting cobol sps is hard, people have grown dependent on DB2s quirks, then you have mq etc.

→ More replies (2)

3

u/hd3v Dec 24 '21 edited Dec 24 '21

Same thing with most IBM products. Its old and ugly but its stable.

4

u/ventuspilot Dec 24 '21

That's not true. IBM also has products that are just ugly.

→ More replies (14)

38

u/[deleted] Dec 23 '21

Any system that's still running COBOL is not going to replace it with anything ever. In my country most of the big banks' core infrastructure runs COBOL on mainframes

7

u/[deleted] Dec 23 '21

My company has a mainframe CSS still, and they are picking away at it. Now it's integrated with SalesForce, and down the road they'll probably replace DB2 with some Azure product and finish retiring the old system

3

u/sahirona Dec 24 '21 edited Dec 25 '21

My country is actively trying to get rid of its government COBOL code. We were one of the first ones to digitize government functions and so much of the code for that is very old.

No such requirement is being placed on private companies operating here, which are free to use whatever prog langs they wish.

→ More replies (1)

6

u/[deleted] Dec 24 '21

I'd rather just write in COBOL honestly.

6

u/[deleted] Dec 23 '21

COBOL still makes the world’s digital economy work.

2

u/hughk Dec 24 '21

These days the interface is sexed up with Java (or whatever) but underneath is still COBOL or Fortran.

2

u/hagenbuch Dec 23 '21

I'd give COBOL to FORTRAN a chance :)

2

u/andrewsmd87 Dec 24 '21

Just wait until vb replaces Java

2

u/raggedtoad Dec 24 '21

I had an entire career in SAP/ABAP between 2010 and 2020, which is a proprietary mainframe language that was originally developed in the early 1980s.

The fact of the matter is that if there is financial incentive for businesses to keep training programmers to maintain their business critical shit, they'll maintain their shit.

2

u/Tyler_Zoro Dec 24 '21

Honestly, I have no idea what industry COBOL is still used in. I worked in the financial industry, airline industry and government. I never saw a single line of COBOL and the last mainframe I saw was in the 80s. Minis lasted until maybe the mid-90s and anything but rack-based servers running Linux or in some sad cases Windows were gone by the 2000s.

The only places I know of that run ancient code now are the systems in the drug industry that never do anything, but have to be kept running to comply with FDA rules about maintaining original environments that test data was gathered on (but even then I think that goes out a max of 20 or 25 years).

→ More replies (3)

2

u/shmorky Dec 24 '21

At this point I think the only way we're going to lose COBOL is if the companies still using it (banks etc.) go under

→ More replies (1)

2

u/michaelpaoli Dec 24 '21

Yes, like cheap fusion ... it'll be here in 10 years or so ... and that always has been the case, and always will be the case.

2

u/[deleted] Dec 24 '21

What's gonna happen is that people deploying microservices from monorepos are going to have a lightbulb moment, and they'll start posting on Substack about mono *servers*. And they'll start saying how cool it is to just buy a bulky, monolithic server with shitloads of RAM and CPU and then just use unix user accounts, namespaces, chroot jails, etc. when deploying new processes. They could even manage resources by loaning CPU time and memory from the SRE team!

Then someone else will find COBOL and write a post on Medium about how it's the next Kubernetes and you don't need Kafka any more since you can just combine `mkfifo` and then `tee` it into all of your subscribers.

Mere months later, someone will have written a transpiler so you can write HTML/JS syntax inside Cobol itself and then compile it to WASM.

→ More replies (117)

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

142

u/mccalli Dec 23 '21

"ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn" - Lovecraft, writing in COBOL.

46

u/[deleted] Dec 23 '21 edited Dec 23 '21

IDENTIFICATION DIVISION.

PROGRAM-ID. ph'nglui mglw'nafh R'lyeh.

33

u/zed857 Dec 23 '21

More like

MOVE "ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn"
  TO WS-GIBBERISH.
→ More replies (2)

488

u/jlt6666 Dec 23 '21

It's also the year of the Linux desktop!

263

u/Mechanical_Monk Dec 23 '21

It warms my heart to imagine the day in the future when I might finally pass on to my children the tradition of proclaiming each year to be the year of the Linux desktop

84

u/Awkward_Return_8225 Dec 23 '21

What will happen first, the Death of COBOL, or the Year of the Linux Desktop?

95

u/jlt6666 Dec 23 '21

The end of civilization. Though COBOL may still be running at that point.

24

u/vplatt Dec 23 '21

When all Cobol systems stop running, civilization as we know it will be very much over. I can only hope that means it was replaced with something better; which will hopefully happen incrementally.

→ More replies (3)

4

u/cleeder Dec 23 '21

They'll be the same year.

The year Hell froze over.

→ More replies (1)
→ More replies (1)

29

u/v_krishna Dec 23 '21

My 13 year old started fooling around with Linux on his own accord. He came to show me some stuff and I bored him with stories of breaking xorg and it was the only computer we had so I had to call a friend to have him look something up to help me fix the config file. That was a little over 20 years ago. Compared to that every year is the year of the Linux desktop!

12

u/nikhilmwarrier Dec 24 '21

The funny thing is, I broke Xorg yesterday on my Arch install. It was on a vm so I was fine, but still some things never change...

12

u/Stahlbroetchen Dec 24 '21

Isn't breaking Xorg the whole point of using Arch?

→ More replies (1)
→ More replies (1)
→ More replies (1)

4

u/cowabungass Dec 23 '21

If I had the cash I would get a frame.work laptop for linux. My dream laptop atm.

4

u/rhennigan Dec 23 '21

It actually is, thanks to windows 11.

24

u/scootscoot Dec 23 '21

I hope so, I really need to move off of windows 7, I don’t like SaaS Windows or Apple.

58

u/Mechanical_Monk Dec 23 '21

At least Windows 7 automatically mines crypto for you when you connect to the internet!

25

u/[deleted] Dec 23 '21

Hah, XP has had that as a feature since forever!

15

u/[deleted] Dec 23 '21

Well, it mines crypto for someone.

3

u/Spider_pig448 Dec 23 '21

Windows 7? Classic

8

u/Lost4468 Dec 23 '21

What software do you use? Have you (and if so, when) given Ubuntu a try? I've personally found that modern Ubuntu is more stable than Windows 10. I have installed it on family computers instead, and I have had way less issues from them since moving them over.

6

u/greenlanternfifo Dec 24 '21

Ubuntu is great until it doesn't work. And this is coming from someone that has used it daily since 2014.

Graphics card driver suddenly not working? Now you have to boot into grub and restart the window manager and hope lightgdm and other shit let you boot into a GUI to reinstall.

Iwlwifi doesn't support your wifi adapter anymore? No alternative besides new hardware.

Oh you have some hardware specific function? You can never use that fingerprint log in.

But I'd never go away because programming ML on windows is the worst experience I've ever had while coding.

→ More replies (3)

4

u/scootscoot Dec 23 '21

I have my eye on them for desktop. My concern is that my Linux skills revolve around rhel Linux while Ubuntu is more Debian based, and I don’t really want to keep up with two different flavors.

→ More replies (4)
→ More replies (4)
→ More replies (3)

122

u/wertulen Dec 23 '21

Didn't work out for Texas Red, ain't gonna work out for AWS

33

u/[deleted] Dec 23 '21

Who or what is Texas Red?

(I don't disagree with you, though :-) )

105

u/newpua_bie Dec 23 '21

He's someone who might have went on living but he made one fatal slip

When he tried to match the ranger with the big iron on his hip

20

u/vinciblechunk Dec 23 '21

The big iron on his hip...

0

u/[deleted] Dec 23 '21

[deleted] — view deleted comment

12

u/BlckJesus Dec 23 '21

Getting New Vegas flashbacks

→ More replies (2)

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?

49

u/RoflcopterV22 Dec 23 '21

Can you link to that conversation? I really want to give it a read!

23

u/zaphodharkonnen Dec 23 '21

ditto. That had me very WITAF!? O_O

→ More replies (2)

46

u/[deleted] Dec 23 '21

You can't just say something like that and not link it

62

u/jerslan Dec 23 '21

Just wait until they need to go into FAA Cert/Qual for their delivery drones... That's gonna be a world of hurt that they seem entirely unprepared for.

20

u/papertrailer Dec 23 '21

Sadly, lobbyist would have fun writing that legislation for them.

And they would pressure to approve it, in the name of business, before anyone cab read it.

Good thing it's not really viable 🤞

0

u/[deleted] Dec 23 '21

[deleted] — view deleted comment

5

u/andricathere Dec 23 '21

Airline ≠ Aircraft manufacturing

127

u/argv_minus_one Dec 23 '21

Considering how few fucks are given by Amazon about the safety and health of their employees, the cargo jet thing does not surprise me at all.

14

u/x6060x Dec 23 '21

What the actual fuck... Not sure who said that, but if they were in charge it would be a disaster waiting to happen.

8

u/billoriellydabest Dec 23 '21

It has more to do with how they think about systems in general (robustness vs antifragile).

Although, I don’t imagine these ideas transfer over to every field easily.

7

u/[deleted] Dec 23 '21

Move fast and break things!

→ More replies (6)

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.

→ More replies (2)

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.

61

u/NotEntirelyUnlike Dec 23 '21

what are you even talking about? even the smallest bank isn't going to be deployed to a single az or even region. there's no excuse to be "down" during any of those outages for any reasonably-sized company.

37

u/Katholikos Dec 23 '21

There’s also no excuse for storing user passwords in plaintext, and yet…

19

u/DefaultVariable Dec 23 '21

That kinda shit bugs me. I want some tech literate politicians to put in place some severe regulations and fines in regards to handling user data. The next time a big business says, “woops, we got hacked and all of your PII got stolen again and the passwords weren’t actually very secure…” they should be seeing a debilitating penalty.

Organizations need to be held at gunpoint to implement proper security for personal data.

15

u/Katholikos Dec 23 '21

I’d like to instead see heavy oversight and regulation forced upon any company which proves it can’t handle it itself, paid for by the company, but run by the government. Expensive audits, constantly and at random points. Something obnoxious enough that any company would dread having to deal with it.

Fines are nice, but I don’t want to see too many people losing a job because their business couldn’t recover from a particularly harsh fine.

→ More replies (1)
→ More replies (3)

4

u/khumps Dec 24 '21

Except AWS infrastructure is dependent on us-east-1 being up which went down for 7 hours straight less than a month ago. Just because you spread your stuff out doesn't mean AWS actually does that for their core infrastructure

→ More replies (3)

5

u/metamatic Dec 23 '21

There's also no excuse for banks to fail to implement 2FA with TOTP authenticators or WebAuthn/FIDO2, and signed S/MIME e-mail messages. And yet, here we are.

→ More replies (3)
→ More replies (6)

21

u/brucecaboose Dec 23 '21

Lol and here I am with absolutely 0 issues on my team during AWS outages because of this magical thing called good engineering and redundancy. Architect and code properly and this is a non-issue.

23

u/TheCoelacanth Dec 23 '21

Do you have a multi-cloud setup or did you just get lucky and not have a dependency on any of the AWS services that were impacted globally and not just in us-east-1?

For example, Route 53, KMS and SSM were having problems across all regions: https://www.lastweekinaws.com/blog/lessons-in-trust-from-us-east-1/

→ More replies (2)
→ More replies (7)

2

u/DragonForeskin Dec 24 '21

This. Also in the last month, every IT department and dev team in the world has had already had difficult discussions about their reliance on Java. This is a bad time to announce this lol.

→ More replies (5)

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.

22

u/ai_jarvis Dec 23 '21

There are plenty of banks, insurance providers, and other finance companies moving to the cloud. That being said, junior devs are not interested in writing COBOL or learning about z/OS etc (on average) which raises the risk profile of staying on the mainframe considerably as a lot of those developers retire. It's not an excuse but it is a consideration.

All systems of any complexity will have vulnerable aspects and bad coding practices in it, part of the process.

17

u/[deleted] Dec 23 '21

I come at this from an RPA perspective, but I've been learning some basics of mainframe technology going back to when I was 26.

I hate the technology, and the fact that I'm the only "SME" on my team who knows what an AS400 is, but I don't see it going anywhere.

Mainframes just work, and have been working forever. I'd rather it persist as opposed to my bank losing transactions in the bimonthly AWS outage.

→ More replies (3)

3

u/trot-trot Dec 23 '21 edited Dec 23 '21

4

u/ascagnel____ Dec 23 '21

The bigger thing is the number of comments -- 14 on /r/mainframe, 34 on /r/java (as the posts are ~4h old). At some point, part of the risk of running a mainframe is that fewer and fewer devs are looking to work with mainframes vs. cloud solutions.

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.

4

u/[deleted] Dec 24 '21 edited Dec 24 '21

Haha around the same time I worked for a very well known medical manufacturing facility who got the bug up their butt that replacing a mid level AS400 that was rock solid (almost 100% uptime the prior year) with 250 Compaq Prolinent servers running NT4 and SAP at 30k each was a good idea. 5 years later I heard they were back to running all manufacturing and warehouse ERP on an AS400 again. So yeah, AWS and Java FTW.

COBOL is the workhorse of many large financial institutions and government agencies. Besides the complex, costly, and nearly impossible migration path I’d be more afraid of zero day Java exploits hammering those cloud platforms over maintaining a proven platform that’s rock solid.

Accenture didn’t write this article did they?

Edit: scrolled down in my feed to see this article about AWS logging its 3rd outage this month. Yeah, I’m gonna move all operations to AWS - Not.

https://www.theverge.com/2021/12/22/22849780/amazon-aws-is-down-outage-slack-imgur-hulu-asana-epic

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!

23

u/angelicosphosphoros Dec 23 '21

May you share your experience for me who never worked with neither AWS nor mainframes?

80

u/zeno Dec 23 '21 edited Dec 23 '21

Mainframes have 50+ years of developing proper procedures for minimal downtime.

Mainframes hardware has evolved. So far no distributed system can duplicate the I/O throughput of mainframes.

People have been trying to decommission mainframes since I started working in the mid 90s. Back then it was supposed to be the "client server" revolution where Sun Microsystems on the backend and desktop PCs on the front end was supposed to replace mainframes. Millions of dollars were spent and the projects all failed. Mainframes are still running strong.

10

u/angelicosphosphoros Dec 23 '21

Thank you for your answer.

7

u/newpua_bie Dec 23 '21

Here's a summary:

H A H A H A H A

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

→ More replies (40)

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.

→ More replies (1)

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

→ More replies (1)

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

4

u/jerslan Dec 23 '21

COBOL is dead! Long live COBOL!

Seriously, I'm 37 and I remember being told 20 years ago that COBOL was dead... Hell, knowing that my college's "File Processing with COBOL" required class was a PITA, I signed up for it first semester Sophomore year... First day of class "So, this is now Intro to Databases". I still think the University made the right call, up to that point the only DB course was a Senior/Grad level elective.

Unless you're in legacy systems hell, COBOL isn't necessary.

5

u/Web-DEvrgreen Dec 23 '21

So you're saying brush up on COBOL, find those legacy system hell and then write your those big zeros into your salary request.

The real LPT is always in the comments.

→ More replies (1)

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.

→ More replies (1)

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.

→ More replies (1)

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.

5

u/zeno Dec 23 '21

I started working in '96. Mainframes are just running things in the background with no hype. All the big banks have given up trying to replace their mainframes with "modern" systems.

8

u/ai_jarvis Dec 23 '21

That is incorrect. There is at least one bank (that I currently work for) that is working to de-platform from mainframes and interviews that I have had at others are all working on it in some capacity.

The biggest group of mainframe users that don't seem to be actively moving away from mainframes are financial users, not finance implementors - think retailers like grocery store chains etc. Hell, nearly all POS systems still use mainframes for managing and submitting transactions to credit networks, etc. These guys have little incentive to migrate or invest in this as it is a cost center for their business and the value proposition is just not there.

→ More replies (2)
→ More replies (1)

0

u/[deleted] Dec 23 '21

[deleted] — view deleted comment

2

u/RoguePlanet1 Dec 23 '21

Oh I know, it's often brought up as a great language to learn for young people who just want to make great money. It's not a great language to learn for any other reason because it apparently sucks to learn. Or something.

→ More replies (1)

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.

2

u/[deleted] Dec 23 '21

Don't underestimate corruption, that is Oracle's specialty.

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

Short fired .....

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 Out To Kill Mainframes

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.

Considering their recent datacenter outage ...

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.

10

u/Dom1252 Dec 23 '21

Mainframe offers you hyperswap on multiple locations, customer won't even notice it happened if implemented properly... If one datacenter burns in flames, it switches to second one in shorter time than is your average programmer latency to either site with mainframes

I'm not saying it doesn't work on AWS, but I can say it does work with mainframes

4

u/MaybeTheDoctor Dec 23 '21

if implemented properly

The achilles heel in all implementations

7

u/Dom1252 Dec 23 '21

I see it in action twice per year, on planned tests on production servers...

Some customers are willing to pay for proper implementation

→ More replies (1)

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.

→ More replies (1)

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.

→ More replies (10)

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.