3 ms·
The savings only really works at scale though right. I've worked in plenty of engineering departments with 200 engineers and essentially 5 operators. You need
by steveBK123 3y ago
The savings only really works at scale though right.
I've worked in plenty of engineering departments with 200 engineers and essentially 5 operators. You need bare minimum 3 of them for holidays/timezones and key man risk reasons.
So you can maybe help a 200 person org save 0.5-1% of their lower paid staff?
Is your bill + engineering integration costs going to be less than $200-400k/year?
- jacobr1 3y agoDepends on how much the non-operators are using the data. In SaaS companies it is common for the engineering teams to own the performance of their sub-systems, which entails the need for instrumentation, monitoring, dashboards, alerting and investigative tooling. The trend has been to combine things like logs, distributed tracing, APM, error collection and general metrics collection into the same toolset so that you can more easily cross-coordinate between them when tracking down what is happening in a large system. microservices architecture and "devops" make this a much bigger thing requiring every team to take on some aspect of operational capability.
- jeffbee 3y agoI've worked in 100-person groups where everyone spent all of their time trying to figure out what the hell the system was doing because it did not have tracing or logging.
- steveBK123 3y agomicroservices I take it ;-) ?
- jeffbee 3y agoYes it was one of those extremely bad architectures where every little thing that could have been a library function was an RPC instead and all the services were running in containers with .1 CPU quota and 64MB of memory.
- steveBK123 3y agoSomeone needs to explain to me the purpose of containerizing architecture down to such small subcomponents that they could have run on my Windows 98 machine 25 years ago. At some point you're wasting a lot of time/bandwidth on RPC, and/or memory on all the data copies across process boundaries. So its bigger and slower, harder to orchestrate, harder to monitor, and.. I'm sure there's some positives somewhere.
- jeffbee 3y agoI don't get it either, and the people who designed and built that system were idiots, so I didn't get a good impression of such fine-grained services. I am comfortable with services that are much larger, such as "store this document" or "classify an email as spam or not".