Live data from Hacker News

Millennials and Mainframes: How to Bridge the Gap

info.model9.io

101–110 of 163 posts

Re: Millennials and Mainframes: How to Bridge the Gap

#101

Earlier quoted context omitted.

You want a mainframe if you want your system designed by engineers and not web developers. The IBM mainframe system is called "Z" for zero downtime. Banks and Airlines use systems that haven't needed to be rebooted in decades. (This is a little oversold, but that's the selling point.)

Banks and Airline systems go offline all the freaking time. Just the other day I told the post office attendant their system was back online, as the cursor started blinking again. Telltale sign of mainframe style computing.

When you turn off your laptop, does Google go down?

Re: Millennials and Mainframes: How to Bridge the Gap

#102
post #28

Ok, maybe this is a silly question, but I am a millennial.... Question: what is a mainframe and why would I want one? In my mind I think of it as a big, but inelastic, compute resource. If that's true, why wouldn't I want to use something horizontally scalable instead?

Try this: Ok, maybe this is a silly question, but I am {...}.... Question: what is a house and why would I want one? In my mind I think of it as a big, but inelastic, tent. If that's true, why wouldn't I want to just get multiple tents instead? A mainframe is the kind of computer you can buy and set up, turn on, and run for two decades (or more, if you like) non-stop. It doesn't need reboots, it most often doesn't ev…

and everything inside is already virtualized the memory, the processors, the hardware, the power, everything, it can multiple operating systems.

Re: Millennials and Mainframes: How to Bridge the Gap

#103
post #69

Earlier quoted context omitted.

Try this: Ok, maybe this is a silly question, but I am {...}.... Question: what is a house and why would I want one? In my mind I think of it as a big, but inelastic, tent. If that's true, why wouldn't I want to just get multiple tents instead? A mainframe is the kind of computer you can buy and set up, turn on, and run for two decades (or more, if you like) non-stop. It doesn't need reboots, it most often doesn't ev…

Except when they do go down it can be a catastrophic business interrupting event. Which is why the cloud model of assume everything is going to break and all your hardware is disposable works much better (IMO).

AWS, Google Cloud, and Azure break more often than our mainframes. In this case, the cloud model is a con, essentially the self checkout lane at Walmart. You're paying more for the same ability you had before.

"Well, you want redundancy right? Well you're supposed to be redundant across AZs, and then regions, and then you're going to have to have disparate vendors to mitigate sole vendor risks." And then we're right back to hosting our own mainframes in our datacenters.

Re: Millennials and Mainframes: How to Bridge the Gap

#104
post #101

Earlier quoted context omitted.

Banks and Airline systems go offline all the freaking time. Just the other day I told the post office attendant their system was back online, as the cursor started blinking again. Telltale sign of mainframe style computing.

When you turn off your laptop, does Google go down?

What does that have to do with anything?!

Re: Millennials and Mainframes: How to Bridge the Gap

#105
post #99
post #82

Earlier quoted context omitted.

Given that Intel leads cpu performance, How can mainframes be that much better at single node performance than x86 servers ?

Intel leads in x86 performance and comparing performance of System z CPU to x86 is not exactly trivial task as zArchitecture is "uber-CISC" with instructions like "give me SHA256 of this part of memory" that also typically runs on 4+GHz clocks (and the "CPU book" has TDP of several kW). But main part of the performance advantage (be it perceived or real) is incredible memory and IO bandwith combined with large caches…

> On the other hand, you can get rack-mount x86 server with several TB of RAM for fraction of price of mainframe which is exactly the hardware for new applications that would otherwise be best served by mainframe.

I expect the largest one of these is still a fraction the size of the largest mainframe, at least for processor power (e.g. 224 cores[0] compared to 1700[1]). Maximum memory, though, is 32TB, which isn't exactly huge compared to 12TB [0] or 24TB [2].

[0] https://www.supermicro.com/products/system/7U/7089/SYS-7089P...

[1] https://en.wikipedia.org/wiki/IBM_zEnterprise_System#z14 (Not saying they're necessarily equivalent in performance, but they might be, as you point out)

[2] https://www.supermicro.com/products/system/7U/7088/SYS-7088B...

Re: Millennials and Mainframes: How to Bridge the Gap

#106
post #69

Earlier quoted context omitted.

Except when they do go down it can be a catastrophic business interrupting event. Which is why the cloud model of assume everything is going to break and all your hardware is disposable works much better (IMO).

AWS, Google Cloud, and Azure break more often than our mainframes. In this case, the cloud model is a con, essentially the self checkout lane at Walmart. You're paying more for the same ability you had before. "Well, you want redundancy right? Well you're supposed to be redundant across AZs, and then regions, and then you're going to have to have disparate vendors to mitigate sole vendor risks." And then we're right…

Clouds reinvent mainframes. They're still cheaper, run more FOSS, and have more talent available. They're a better form of lockin than mainframes.

Re: Millennials and Mainframes: How to Bridge the Gap

#107

Earlier quoted context omitted.

AWS, Google Cloud, and Azure break more often than our mainframes. In this case, the cloud model is a con, essentially the self checkout lane at Walmart. You're paying more for the same ability you had before. "Well, you want redundancy right? Well you're supposed to be redundant across AZs, and then regions, and then you're going to have to have disparate vendors to mitigate sole vendor risks." And then we're right…

Clouds reinvent mainframes. They're still cheaper, run more FOSS, and have more talent available. They're a better form of lockin than mainframes.

[deleted]

Re: Millennials and Mainframes: How to Bridge the Gap

#108
post #100

Earlier quoted context omitted.

Data bandwidth probably

Bandwidth and reliability . It's in general hard to swap out cpus while running db transactions on commodity x86 hw.

In theory you can hot-swap CPUs on x86 (with slightly hillarious fact that primary use of the Linux's CPU hotswap support is suspend to disk on laptops) but hardware that supports it and it really works is rare to non-existent.

Re: Millennials and Mainframes: How to Bridge the Gap

#109
post #49

The way the article is describing millennials is from someone who has an outsiders view and a poor understanding. The things millennials do are not because millennials have wildly different values, they're because the world changed. Everyone in business learned giving pensions, training people and retaining people doesn't pay off. The post-ww2 bubble of prosperity has let out its air. That environment no longer exist…

> Everyone in business learned giving pensions, training people and retaining people doesn't pay off.

...in the short term.

Re: Millennials and Mainframes: How to Bridge the Gap

#110
post #26

Earlier quoted context omitted.

To be brutally direct, why do you think mainframes should not survive "in the coming decades"?

Asking out of complete ignorance: What can a mainframe do that other kinds of machines can't? I barely understand what a mainframe is or why you'd use one over other technologies.

Channel I/O was something I wanted on all my desktops and servers. It helps mainframes get their high utilization ratio and throughput:

https://en.m.wikipedia.org/wiki/Channel_I/O

Post reply on HN