You're calling it 'gatekeeping', but in my experience the latter position is mostly an expression of _frustration_. Dealing with the fallout from dozens of diff

You're calling it 'gatekeeping', but in my experience the latter position is mostly an expression of _frustration_. Dealing with the fallout from dozens of different decisions by engineers and directors to build "for scale" without the proper understanding of the costs involved in doing so makes many of us react with exasperation to suggestions in that vein. We rarely have to convince someone that they _do_ need scalable highly available software - mouthing the idea from across the room is generally sufficient to make a director sign off on such a plan. It's convincing people that the costs those approaches inflict (which can be very difficult to explain, even to other engineers) are _not yet warranted_ that tends to be hard.