Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

REST In Action: The Live Coverage Platform at the New York Times

1.109 visualizaciones

Publicado el

Scott Taylor - Sr. Software Engineer, The New York Times
WordPress 4.4 Release Lead
WordCamp US
Philadelphia, PA
December 4, 2015

Publicado en: Internet
  • There are over 16,000 woodworking plans that comes with step-by-step instructions and detailed photos, Click here to take a look ◆◆◆
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • The #1 Woodworking Resource With Over 16,000 Plans, Download 50 FREE Plans... ■■■
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí
  • There are over 16,000 woodworking plans that comes with step-by-step instructions and detailed photos, Click here to take a look ◆◆◆
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí

REST In Action: The Live Coverage Platform at the New York Times

  1. 1. REST In Action: The Live Coverage Platform at the New York Times WordCamp US Philadelphia, PA - December 4, 2015
  2. 2. Scott Taylor • Core Developer, WordPress
 Release Lead for 4.4 • Sr. Software Engineer, The New York Times • @wonderboymusic on Twitter/ Instagram/Swarm et al • I like Music, NYC, and Mexican food
  3. 3. 2013 - Present Me at the New York Times
  4. 4. WordPress at the NYT now • some “legacy” blogs • Lens - Photography blog • First Draft • some internal corporate sites • NYT Co. • Women of the World • Times Journeys • The Live Coverage platform • some forthcoming International projects
  5. 5. WordPress 4.4 Lead • REST API (Phase 1) • Term Meta • Responsive Images • WordPress as oEmbed Provider • Tons of under the hood stuff
  6. 6. Blogs Team at The New York Times
  7. 7. Blogs at the NYTimes • NYT used WordPress very early • NYT was an early investor in Automattic • Multisite • ~80 blogs at the height of blog mania - the 00s were the glory days for Blogs and WordPress • Many blogs used Live Blogging
  8. 8. When I arrived: Legacy Blogs Codebase • Separate from the rest of the NYT’s PHP codebase • Global NYTimes CSS and JS, CSS for all Blogs, custom CSS per-blog • A universe that assumed jQuery AND Prototype were loaded on every page in global scope • Challenging amounts of what could generously be called “technical debt”
  9. 9. <html> <head> <script src="prototype.js"></script> <script src="jquery.js"></script> </head> <script> jQuery('#good-times').click( ... ); $$('.prototype').whatever(); </script>
  10. 10. What could possibly go wrong here?
  11. 11. • Inline HTML from 2008 that assumes Prototype will still be a thing in 2015, stored in post_content • Widgets and inline code that add their own version of jQuery/Prototype, because YOLO • Even better: widgets/modules from other teams that use a different version of jQuery … at times there could be 4 jQuerys on the page (and 4 different versions at that) Things Like ….
  12. 12. <script src=" lib/jquery/jquery-1.6.2.min.js"></script> <script src=" jquery-1.7.1.min.js"></script> <!—- also bundles jQuery --> <script src=" vhs-2.x.js"></script> <script> NYTD.jQuery(document).ready(function ($) { ... }); </script> All the jQuerys
  13. 13. No shared modules • Code/HTML markup can get out of sync with other projects regularly: header, footer, navigation • The CSS and JS files were split across multiple SVN repos - changes to global assets can affect us without us knowing. Fixing the code requires scouring through multiple repos.
  14. 14. At the NYT • No WordPress Comments: There is an entire team that deals with these for the site globally, in a different system called CRNR • No Media: There is another CMS at the Times, Scoop, which stores the images, videos, slideshows, etc • WordPress native post-locking: This only landed in WordPress core in version 3.6 (we have yet to reconcile the differences) • There is layer for Bylines which is separate from Users: Our users are employees authenticated via LDAP, most post authors don’t actually enter the content themselves
  15. 15. NYT5: The New Frontier My arrival at the New York Times coincided with the NYT5 project, already in progress
  16. 16. NYT5 • Development requires Vagrant environment • “apps” are Git repos that require Grunt to transpile the codebase - you can’t run your repo as a website: it has to be built • Impossible to create a “theme” this time with shared JS and CSS. CSS is SASS build, JS is Require build - both dynamically built for each app. • PHP has Composer dependencies and uses namespaces - the directories are expanded via Grunt in accordance with PSR-0 Autoloading Standard
  17. 17. require( ['jquery'], function ($) { $('#cool-link').click(...); } ); require( ['jquery/1.9'], function ($) { $('#cool-link').click(...); } ); require( ['jquery/2.0'], function ($) { $('#cool-link').click(...); } ); Require.js fixed the jQuery problem
  18. 18. NYT5 Dealbreakers • We can’t just point at WordPress on every request and have our code figure out routing. Routing happens in Apache in NYT5 - most requests get piped to app.php • Because PHP Namespaces are used, WP has to load early and outside of them (global scope) • On the frontend, WP cannot exit prematurely before hitting the framework, which returns the response to the server via SymfonyHttpFoundation
  19. 19. Apache NYT5: app.php Route to NYT5 Blogs app - Load initial files
 - Bootstrap WP - Capture WP content - WP complete - Initialize app
  20. 20. NYT5 Advantages • “shared” modules - we inherit the “shell” of the page, which includes: navigation, footer, login, etc. • our nyt5 theme doesn’t need to produce an entire HTML document, just the “content” portion • With WP in global scope, all of its code is available even when we hit the MVC parts of the NYT5 framework. • WP output is captured via an output buffer on load - it’s accessible downstream when the app logic is running.
  21. 21. $wp_query = new WP_Query(); $GLOBALS['wp_query'] = ... 
 function wp_thing() { global $wp_query; . . . } GLOBALS!!!
  22. 22. This could be solved namespace WP;
  23. 23. Namespaces namespace WP; class Query {} function get_post_meta() {} . . . new WPQuery(); WPget_post_meta(); . . . namespace WP; new Query();
  24. 24. Blogs in Transition
  25. 25. Overall: Bad News for Blogs • Blogs were duplicating Section Fronts, Columns:
 Mark Bittman has column in the paper.
 The column also exists on the web as an article. 
 He contributes to the Diner’s Journal blog. 
 There is a section front for dining. 
 He also has his own NYTimes blog. Why? • Blogs and WordPress were combined in everyone’s mind. So whenever WordPress was mentioned as a solution for anything, the response was: aren’t blogs going away? #dark
  26. 26. But we still had…
 First Draft Lens Live Coverage
  27. 27. 2014 Midterm Elections required new Live Blogging tools
  28. 28. 2008: Live Blogs at the Times • A Blog would create a post and check “Start Live Blogging” • the updates related to the post were stored in custom tables in the database • the APIs for interacting with these tables duplicated tons of WordPress functionality • Custom Post Types didn’t exist until WordPress 3.0 (June 2010) - the NYT code was never rewritten to leverage them (would have required porting the content as well)
  29. 29. Live (actual) Blogs: Dashboards/Dashblogs • A Live Blog would be its own blog in the network, its own set of tables • A special dashboard theme that had hooks to add custom JS/CSS for each individual blog, without baking them into the theme • Making an entirely new site in the network for a 4-hour event is overkill • For every 10 or so new blogs that are added, you are adding 100 new database tables - gross!
  30. 30. What if… • Instead of custom tables and dupe’d API code, new object types: events and updates! • To create a new “Live Blog”: create an event, then go to a Backbone- powered screen to add updates • If WP isn’t desired for the front end, it could be the backend for anything that wants a JSON feed for live event data • Using custom post types, building a Live Event UI that looks like the NYT5 theme would be nominal
  31. 31. • Built an admin interface with Backbone to quickly produce content - which in turn could be read from JSON feeds • When saving, the updates post into a service we have called Invisible City (wraps Redis/Pusher) • Our first real foray into using the REST API • Our plan was just to be an admin to produce data via self-service URLs What we did
  32. 32. Live Events, the new Live Blogs: Complete Rewrite of 2008 code •{event} and{event}/ {update} • Brand new admin interface: Backbone app that uses the REST API. Constantly updated filterable stream - Backbone collections that re-fetch on Heartbeat tick • Custom REST endpoints that handle processes that need to happen on save • Front end served by WordPress for SEO, but data is received by web socket from Invisible City and rendered via React
  33. 33. Responsive on Mobile
  34. 34. An “Interactive Promo” on an article page
  35. 35. 2015: “Blogs” team becomes “WordPress” team, joins the Interactive News team
  36. 36. Guess What? • Would rather use Docker instead of Vagrant • PSR-0 is now PSR-4 • Grunt is now eschewed in favor of Gulp • RequireJS is ok, but I’d rather use Browserify • PHP is cool, but why don’t we use Node and React?
  37. 37. Interactive News Team • Mostly independent • Mostly special News projects • Mostly use whatever language you want • Mostly does not use NYT5 • Is open to using WordPress, but just as often, does not
  38. 38. What is a Live Coverage platform?
  39. 39.{event} Request is served by WordPress, PHP generates markup React wraps the "posts" area JS listens to Web Socket Updates are added on the backend (OR via SLACK!) React updates the content
  40. 40. the elections code became useful for Breaking News
  41. 41. WordPress + REST
  42. 42. Register a route: register_rest_route( ‘nyt/v1’, ‘/live-events/(?P<post_id>d+)’, [ ‘callback’ => [ $this, ‘liveEventRoute’ ], ‘methods’ => WP_Rest_Server::CREATABLE ] );
  43. 43. Handle the route: public function liveEventRoute( $request ) { $post_id = $request['post_id']; $response = new WP_REST_Response( [ 'results' => . . ., ] ); return $response; }
  44. 44. Some REST API gotchas…
  45. 45. Most plugins only handle POST • WP-API and Backbone speak REST • REST will send you requests via 
 GET, PUT, DELETE, POST and friends
  46. 46. $hook = add_menu_page( ... ); add_action( "load-$hook", 'callback' ); function old_custom_load() { if ( 'POST' !== $_SERVER['REQUEST_METHOD'] ) { return; } ... } function new_custom_load() { if ( 'GET' === $_SERVER['REQUEST_METHOD'] ) { return; } ... }
  47. 47. WordPress becomes a web service • Monolithic mindset needs to transition into how to make it into a bare metal service provider • The serving of requests should be loosely coupled from objects like WP_Query • WordPress needs to become supportive of concurrency
  48. 48. Custom JSON Endpoints for GET • We do not hit these endpoints on the front-end • We have a storage mount that is fronted via Varnish and Akamai • JSON feeds can show up on the homepage of the NYT to dynamically render “promos” - these have to massively scale
  49. 49. HTTP is time-consuming • It is easy to lose track of how many things are happening on the 'save_post' hook • Admin needs to be fast • The front end is typically cached, but page generation shouldn’t be bogged down by HTTP requests • Anything which is time-consuming should be offloaded to a separate “process” or request who response you don’t need to handle
  50. 50. wp_remote_post( $url, wp_parse_args( [ 'timeout' => 0.01, 'blocking' => false ], $args ) ); Fire and Forget* * Stolen from Mark Jaquith’s nginx cache invalidation technique: wp_remote_get( $url, [ 'timeout' => 0.01, 'blocking' => false, 'headers' => [ 'X-Nginx-Cache-Purge' => '1' ] ] );
  51. 51. Custom REST Endpoints for POST • Use fire-and-forget technique on 'save_post', instead of waiting for responses inline. You can still log/handle/re-try responses in the separate request. • Most things that happen on 'save_post' only need to know $post_id for context, the endpoint handler can call get_post() from there
  52. 52. Trigger the process: NYTAdminREST::async_request( '/varnish-invalidation', [ 'urls' => $urls ] );
  53. 53. Questions?