4 ms·
Two reasons, mainly. First, it handles ebbs and flows in requests much more gracefully. It's cheap to throw everything on a queue, and handle it as the system
by silisili 4y ago
Two reasons, mainly. First, it handles ebbs and flows in requests much more gracefully. It's cheap to throw everything on a queue, and handle it as the system allows.
Secondly, it's decoupled from your application. Trying to do things directly works for a while, then you do an in memory array, then your application crashes or gets updated and lost those messages.