Went ahead and implemented the API/async approach since it was pretty easy. This still can hang a request on our server for a few seconds while we wait for the heroku instance to spin up. However, the page itself will load first. Now the users can start reading the text and we'll deal with the inessential slack stats in the background.
Went ahead and implemented the API/async approach since it was pretty easy. This still can hang a request on our server for a few seconds while we wait for the heroku instance to spin up. However, the page itself will load first. Now the users can start reading the text and we'll deal with the inessential slack stats in the background.