Re:After Alaska Airlines planes bump runway, a scramble to ‘...
by hn_throwaway_99 on Saturday February 18, 2023 @11:22AM
(#34848065)
But calling something an "internal architectural problem" implies things are fundamentally designed wrong, and the code needs a rewrite. My point was the architecture can definitely be fine, but you can still have bugs (even catastrophic ones) because someone left out a `synchronized` keyword somewhere.
[ Parent
| on HN ]
Re:After Alaska Airlines planes bump runway, a scramble to ‘...
by thrashh on Saturday February 18, 2023 @01:21PM
(#34849461)
It could still be
For example, one way to use SQL is to escape your parameters and then concat them straight into your SQL string. However, if someone leaves out an ‘escape’ somewhere, you have a major security incident
The other way is to pass parameters separately as data to your SQL driver. It completely negates the problem
If you’ve chosen the first way in your project already, you’ve committed to a major internal architectural problem. In the same vein, maybe if your code requires sprinkling ‘synchronized’ everywhere, you did it wrong
But that said, we don’t know what actually is the problem since it’s just a marketing statement saying that high load was the cause and that doesn’t tell us anything