With fiber pause resume the onus is put on the IO library writer. Someone has to write a MySQSL library that used threads. The advantage is that this is completely transparent to the library user. A goliath user need not be concerned about events or fibers when using MySQL.

In contrast, a node user must specify a callback every time they make a query. I don't know if the library writer has to do anything special.