title: Best Practice for Laravel Asynchronous Requests
body: <p>I have a Laravel application. The application loading perfectly fine, when I only make 3-10 API per page in my controller.
  Now, I start to see the latency when I start making <code>200 API</code> requests per page in my controller.</p>
  
  <p>Since Laravel is MVC. </p>
  
  <p>All the code in the controller need to be fully executed and finished, and then it will send all the data/variables to the view.
  But that is leading to a lot of latency.</p>
  
  <p>I’m thinking to perform that APIs call asynchronously, but I am not sure which one is the best move, </p>
  
  <p>I did a quick search, I found : </p>
  
  <ul>
  <li>PHP cURL Async: <a href="http://php.net/manual/en/function.curl-multi-init.php" rel="noreferrer">http://php.net/manual/en/function.curl-multi-init.php</a></li>
  <li>Laravel Async: <a href="https://laravel.com/docs/5.1/queues" rel="noreferrer">https://laravel.com/docs/5.1/queues</a></li>
  <li>PHP Promise: <a href="https://github.com/reactphp/promise" rel="noreferrer">https://github.com/reactphp/promise</a></li>
  </ul>
  
  <p>Any directions/suggestions on this will mean a lot to me, and others that faced this issue.</p>