June 13, 2025 at 12:00 am
Comments posted to this topic are about the item What is a Failed Deployment?
June 13, 2025 at 4:41 pm
Your comment on storing the data and failing to notice a downstream process is something that opens up a can of worms.
In the old days, a web app might store its data in a SQL Server instance. That instance would replicate its data to a staging instance with a longer retention strategy than the web front-end. As DBAs would be maintaining replication, and probably how the staging instance presented the information for consumption, we had visibility and responsibility for the whole pipeline.
These days, the web app probably puts a JSON message onto a queue. This lands in some form of blob. storage and a back-end app processes the JSON messages. Eventually, the data ends up in a DB of some kind.
The responsibilities have become blurred. No one owns or admits responsibility for the whole pipeline.
Success has many fathers, but disaster is always an orphan. The teams involved have both the means and motivation to say "not my problem, guv".
June 13, 2025 at 9:10 pm
It also means teamwork across dev, qa, ops, etc. is really important to solve problems efficiently.
June 14, 2025 at 4:38 am
How very ironic. Just this week I was using that same DORA page for a presentation at work, before reading it here. I can't help but think that the mentions mentioned by DORA's 4 keys to measure and track are far more important than I've ever considered before. I don't believe we, at work, have considered them much, until now. At least I hope that we pay more attention to them. I also know that at work other pressing issues, often of an office political nature, tend to trump all else. I don't know what to call this. Is it the urgent taking precedence over the important? Is it something else? I'm saying that some other issues may push the 4 keys aside and out of sight.
Rod
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply