[lenerdenator]

That's something I've noticed: the way we treat systems developed to work on data is _completely_ different from systems developed to work on, idk, oil.

You can build data refineries (ETF) same as an oil refinery. The difference is, the engineers who build the oil refinery create manuals and standard operating procedures to operate the refinery, because if they don't, then the new board operator will press the wrong button and blow out every window in a five-mile radius.

When you build a data refinery, no one documents _anything_ no matter how many times you ask engineers on the team to do it. Will it blow up in a massive fireball if you do it wrong? No, but it will corrupt data and have a business consequence. You can keep the 40 different microservices for the data refinery in your head though, right?

[pixl97]

Oil refineries don't have backup restore points.

[lenerdenator]

Depending on what exactly it is that you're storing or processing, neither does data.

Think sensor data and the sensor is a vital signs monitor in a hospital. The service that reads its output and stores it glitches out due to some sort of misclick by a user. It distorts the fact that the patient has an arrhythmia. Or a service that reads off the medication dosages for a patient for a pharmacist is stuck on a single message.

[nottorp]

I strongly doubt they're debating microservice vs monolith in that area.

Maybe you should try an example with cat photos.

[lenerdenator]

Used to work for an EMR company. This is very much a real-world concern, I assure you.