The more complex the system, the less likely the guess is correct. The more senior and experienced in the systems our people are, the more likely the guess is correct. The sniper strategy can be very fast if the guesses made are correct. Let’s compare both techniques and see their pros and cons. Now we have two approaches to the same problem: the sniper approach that can eliminate the possible root causes one by one or the general approach that likes to see the big picture and play a strategy to divide and conquer the enemy. But if not, it can end in a whirlpool of attempts, waste of time, and frustration. If intuition is good, this technique can deliver a solution in record time. The engineer is acting as a sniper, selects a target (guess), and removes it (sniping). This is the guessing and sniping strategy. This cycle can repeat several times, prolonging the problem-solving to several hours or even days or weeks. There is an issue in a very complex system with a lot of moving parts and someone immediately thinks about a very likely root cause and applies the solution, just to discover that this was not the cause. I’ve seen the previous approach thousands of times. The day is finishing, and the issue persists. The team rolls back the component release with the same result. New idea, “last week we updated the front end component of the product, and probably some of them are not being displayed.”. Sharding removed, cache rebuilt, and at 12:30 p.m., the team realizes that only 50% of the product is available. 
Let’s remove the sharding it will increase the cost temporally, but the issue will be solved” One or more nodes are probably misbehaving. The same team member arrives with another idea: “probably is the sharding at the cache management.
after the cache rebuild, the issue persists. It will take 30–40 minutes to complete and show the results on the page.Īt 11:00 a.m. One team member says that most likely the problem is at the ETL responsible for the product cache that feeds this selector and runs at 9:00 a.m., so he is going to manually rebuild this cache. The team owning the e-commerce site starts the investigation. and the team receives an incident: “The product selector on the first page of our e-commerce is showing only 50% of the product,” problem-solving starts.
0 kommentar(er)
