Yes. I saw the last days of a VMS cluster (actual VAX not Alpha) system being ported to windows/vb/com/asp. The speed difference was actually incredible. It ended up on a mediocre single Xeon 500MHz P3.
At the end of the day, the windows based system was just as reliable as far as nines went and tens of times faster.
This was only just recently replaced with asp.net I understand. They got nearly 20 years out of each rewrite.
Yes it was a "hardware lock" i.e. the holder of the spoon was allowed to diff their copy with the master on a file share and update that. The spoon was used as a casual weapon to beat idiots as well in jest ;)
Ansible vault, separate repository to the code and you're fine. You're up shit creek if you lose your code too unless you're 100% perfect so there is no distinction in policy.
Hell if you're using vault you might as well chuck the config in with the code. The vault key distribution is what needs to be controlled.
It's perfectly reasonable to put your credentials and configuration into a VCS if any secrets are in ansible vault or something similar.
I reckon they either stuffed it all in as plain text or someone got hold of their source code and found a stupid hole in it and just read the database file off the front end somewhere. It's not unusual for the unclued to stick a database dump on a front facing web server with a "secret url" and just pull that down with curl or something.
Hey, the spoon worked well, until I bought another one and left it in the office :) They had SVN running for everyone a week after and a month later they were running feature branches.
You can, hence my comment about silos. The interface is rarely well defined enough to be able to abstract it over a network boundary from experience. One of the things I see in a lot of monoliths is leaky abstractions and they are really difficult to reign in.
We tend to go for throwing related web front and and API endpoints into the same ball of mud silo and back end that directly with the storage and cache services. We scale those silos up and partition across tenants too. I think a couple of the silos are around the 1 million LoC size now as well.
I'd argue it's cheaper scaling out the monolith or introducing isolated functional silos and scaling them out than even bothering migrating everything to microservices. Also you certainly can't port a complex monolith to microservices; you have to start again. We're quite happily able to shift 15,000 requests/sec from over 2000 http endpoints with a monolith and our kit is at ~20% capacity. Need more? Slice up a silo some more.
Key aspect when you design the monolith is not building a spaghetti monster. If X doesn't need to talk to Y, put a wall there (package level)
Indeed. Apparently some of the human race loves suffering!
To be honest, even though we were just pulling TortoiseSVN into most of the companies, some people just couldn't figure it out even after being bought books, reading the manual AND sitting in training sessions for hours where we hand-held them through every day use cases.
A lot of the companies, software was a function of the business, not the business itself. There was no motivation for the staff to do anything other than minimal effort or even research what their job was about. There was no pride, no ingenuity or creativity. Inevitably this descended into chaos and then I got hired to unfuck the places. Some places you couldn't fix because they were too cheap, too lazy and didn't want to make a change because they were in denial that the poo was actually already over the fan blades.
It was depressing and if I'm honest it made me physically ill and I folded the company and got a permanent job with a company that wielded the clue stick.
About 50% of the companies I consulted for between 2004-2013 had no issue tracker. Most emailed and/or emailed spreadsheets around.
What's even more shocking is about 25% of them didn't even use a VCS, most relying on some poor guy to sit there with a diff tool and merge everyone's shit into something cohesive. One company used a wooden spoon as an ownership lock.
Yeah a big chunk of that was consultancy, support, Oracle licenses. TCO was going to be around £500k for 5 years.
The whole platform got replaced with SQL Server on a clone PC server in the end which cost less than £10k. No fan of Microsoft but there was no competition. And the tooling was far better!
Back in about 1999, I was working for a big corporate and one of our Oracle admins lost her shit and had a meltdown, think it was around 8i era. She just got up and walked out shouting "fuck this fucking shit, I quit". This was on a freshly delivered HP N-Class HPUX box and they just couldn't get it to run after a month of going back and forth between HP and Oracle.
I bumped into her last year at Ansible Fest London and she was still angry about it 17 years later!
And that's what Oracle does to your soul :)
Edit: that N class and Oracle NEVER got deployed in the end. It just sat there unused, licenses weren't renewed, it got sheepishly powered down after a few months to save electricity and it got chucked in a skip after 5 years. About £200k of expenditure down the pan.