7 ms·
TechCrunch Open Sources Its WordPress Async Task Library
- benologist 12y agoThis is a poor solution for having a page slowed down by dozens of 3rd party ads/trackers/etc.
- alexkhadiwala 12y agoWe don't love that the ads team requires so many placements and that AOL requires so many trackers, but we worked to speed things up where we could
- taylorbuley 12y agoThis makes a poor distinction between server-side code (for which async tasks seem designed) and client-side code created by third parties that slows down the experience on a page that's already been downloaded.
- wdewind 12y agoWow, async tasks on top of WP? You are truly heroes, in a sick and twisted kind of way. Nice work.
- taylorbuley 12y agoThe comments section isn't open, so I'll ask the authors a question here in case they see it: WordPress has had async tasks for a very long time in the form of single scheduled WordPress cron items. How is that approach insufficient for tasks such as rebuilding items like Crunchbase "cards"?
- joshfraser 12y agoThey're talking about the frontend being blocked, not the backend.
- taylorbuley 12y agoTypically my design approach for this is to use cron items to pre-compute components so that they don't have to be computed (nor templated, ideally) at runtime.
- dreamfactory2 12y agoIs this any different to cache-warming? What kind of percentage of page loads are affected?
- cheald 12y agoAt Mashable, we did something similar, except we just used Sidekiq. We'd built a lot of functionality in Ruby, which included ActiveRecord classes for Wordpress tables (which makes working with Wordpress's table hierarchy actually sane, and it's insanely useful to be able to get to your DB as objects in a console), so we could interact with Wordpress directly. Actually queueing Sidekiq jobs is pretty trivial - you just need to be able to talk to Redis. Our frontend doesn't actually use Wordpress any more, which was vastly eased by this approach; being able to decouple the backend and frontend made it surprisingly easy to obviate the front-end portions of the product.
- Gigablah 12y agoThis is an amusing amount of press over what is essentially a PHP application making a POST request to itself.