416 karma · joined August 2, 2015
Back in the late 1990s I was involved in provisioning a large Sun e15k. Not indestructable but nearly.
It broke. You know what happened? The factory roof leaked and poured water onto the DC sub-building which the roof then collapsed onto the e15k which promptly blew up and caused a spectacular fire, halon dump and about a month of work arguing with insurance companies and guys with shovels.
In that circumstance, it doesn't matter what promises the vendor make. That's still all your eggs in one basket.
Buy two and keep one somewhere else didn't help either as the network termination, switching and routing layers were down and all the people using it were about 300 miles away from the backup location anyway. So some poor fucker had to dismantle the backup e15k and disk arrays, bring them in a large truck[1] to the original location and erect a temp DC in a portakabin outside the building.
Edit: We would have been better served with two smaller DCs with off the shelf kit on the same site but different buildings running a mirrored arrangement. All for pocket change compared to a zSeries...
That's what the company I work for now do. We have off the shelf kit,SAN replication, ESX, redundant routing and multiple peers in different locations.
[1] imagine the shit if that truck crashed.
"holy crap I've got to recompile my kernel to get more processes" is so 1995...
I went back to my OO roots and c#/c++ and carried on mostly as I did before. Why?
Simply that its easier to rationalise a large system in terms of objects and actions. Even atypical OO languages like Go use this model.
What I did take away was limited mutability (not total immutability) and some functional paradigms such as map/filter and a well founded opinion that one shouldn't listen to programming religious wars and use what works for you.
So how much is that 1000 mile journey going to cost?
1000/44.94.4561.119= where's my calculator?
Apart from some things like miles and gallons which would require a massive synchronised change that is.
I'd also like it if we drove on the RHS here as well so we can get decent import vehicles.
Also dates in numeric order I.e. yyyy/mm/dd you know like all the other numbers we deal with not dd/mm/yyyy or the crazy mm/dd/yy.
Until then, buy a Lada Niva. No one will want to steal it and it doesn't have anything complicated in it that can be hacked.
Salesforce is the root of all evil. Once you're in the ecosystem, you're stuffed. You know it's bad when the entire business team start running round clucking when the EMEA salesforce instance goes down hard...
AWS is fine. Most of the platform's concepts have real world parallels for example.
It solves the old problem of "so how the hell do I restart this network interface on distro X" as well.
I'm a pragmatist and it does solve a lot of core configuration issues with Linux.
Currently digging a financial company out of a royal mess of 20 years of bad technical leadership leading to sprawling infrastructure and cloud dependencies.
They worked out it's easier to get at our data out and on home territory (cloud, telemetry) than actually have to break into your kit.
I walked out of the house two hours later to him having a conversation with a breakdown van in my car park about the breakdown guy not having a suitable part to fix his van.
I literally have an IMAP box and nothing else.