Reservation is a privilege
If we can, we reserve products during checkout:
Returning users - who have previously made and paid for an order. Their account is more trusted and can reserve products any time.
At normal times, they can reserve products during checkout.
If the there's ongoing DoS attempts, new users are not allowed to reserve ...
I've seen 2 main solutions:
Your products are being reserved for X minutes
I've seen notices like this occasionally, but only on places where inventory really matters (usually ticketing sites).
I've also built a number of eCommerce sites for small businesses, and their preferred solution is always the same:
Just ignore it
It's often just not a critical ...
Abandoned cart management processes are the key to try to verify legitimate orders. Use your expected order patterns even in periods of order spikes. Get engagement from users by nagging them about their abandoned cart. If they don't engage with the email or log back in, even after enticement, you can write-off the order.
Not exactly a security-based ...
You assume that it's a software difference that enabled the Win10 box to survive. But the devices that fell have much reduced hardware. You likely just flooded the CPU/memory of the IoT devices and tablets. They are not designed for even small levels of direct traffic to them. A Windows laptop is.
When playing with network traffic you need to run packet ...
You don't need hping3 to fill your gigabit pipe: the standard ping utility in my Debian creates about 1.3GiB/s when using the flood and data size options. CPU seems to be spent on creating the packets and so at 100% CPU, the only thing you can do is create larger packets rather than more packets.
hping3 with the exact same arguments (flood and largest ...