So if you want to work in this niche, having your own Mainframe will greatly speed up learning the system.
It probably also looks awesome when you market yourself.
So all in all, 25k USD for kickstarting a potentially very profitable career sounds like a bargain ....
Thanks for reading!
The TL;DR is that some might want to rather run 1 or 2 systems (mainframe) instead of 100 physical machines (conventional distributed cattle system).
Now, IBM does make it quite expensive but the mainframe has some pretty cool features like pay-for-what-you-use (which you of course get with the cloud, but not so much if you also want your data in-house).
Anyway, it is a fun beer topic if nothing else :-)
Context: I work for a large organization that used to run several physical Z13 mainframes, all of them containing several sysplexes. If we had issues, an IBM consultant would fly in within the day. We were definitely not IBM’s biggest customer but we were not insignificant for them either.
We had a lot of mainframe support staff (so not people programming for mainframe but people maintaining storage, DB2, z/OS upgrades etc.) and I think even for them, the IBM bill was more or less: we see a large number, no idea why it’s this amount, but we cannot prove it is not right, so I guess we’ll just pay it.
Mainframe billing is really complicated.
However, the biggest thing to remember is that you can and should run Linux on these things as well. Linux on z, or zLinux as it for some reason is called, is just Linux on the redundant and fault tolerant mainframe hardware. Anyone with Linux experience could manage it really, and you would get a pretty damn good platform to build a high availability service on.
Still holding a Hp dos pocket whilst working on all these.
ThOse were the days. Different very much from using a mac to run leela zero using egpu :-)
https://developer.ibm.com/mainframe/2018/01/19/reasons-host-...
Internationally also “MT” messages are used, which is also a file with specified format.
So it doesn’t really matter what stack you run, as long as it can create files and send them out :-)
I doubt there’s a legit use-case for a mainframe even in business environments. All the “reliability” it gives you can be re-implemented on commodity hardware and still come out ahead compared to the costs of buying & maintaining a mainframe.
On th plus side, we’ve basically moved complexity from hardware to software (it was pioneered by Google, a software company, so no wonder) which increases salaries of software people, at the expense of hardware people. So yay for us I guess.
CICS and IMS definitely made it easy to create scalable software decades ago. It is not that different from the frameworks we have invented to make distributed systems viable that you mention, which I find insanely cool.
One of the cool things of running e.g. Ceph is that it exposes a familiar API (POSIX filesystem) which makes things easy to integrate with. The mainframe is like that but for hardware. VMware has similar things to some degree where your VM can be kept alive across hardware failure, but not really on the same level.
Anyway, I will stop here but I could go on for hours :-)
Oh please go on for hours; I'd love to hear more. Any format (blog or just semi-structured brain dumps in comment threads) will feed thoughts :-)
You're incorrect. The most common one is to run legacy software, and not just banks. Insurance, retail, utilities, financial, manufacturing, etc. Some companies have been around before x86 hit the scene and already had significant investments in their in-house computing infrastructure.
Given that it generates like 10k BTU/hr or something like that the drain on the datacenter is non-trivial, so I a running cost was to be expected.
As somebody who started out in the 80s with Apple II and C64 stuff the year before going to college, I always laughed at the old “Star Trek’ episode where the new computer has to tap into the main engine for power. After seeing your new bit of kit, that doesn’t sound so far fetched :-)
Have fun with this beast.