WordCamp GR 2017 – WP-API: The Good, the Bad, and the Ugly – J Andrew Scott
/

WordCamp GR 2017 – WP-API: The Good, the Bad, and the Ugly – J Andrew Scott

ByTim Nolte
J Andrew Scott – http://rubberchickenfarm.com/ History of APIs RSS Advantages Fast & reliable Easy to consume Almost no technical footprint Disadvantages Read-only Static content No authentication No user-driven content (i.e. comments, favorites, etc) DIY API Advantages Dynamic content User-driven content App & user authentication Roles & permissions based Connected applications Disadvantages DIY OAuth Redundant URI scheme Mediocre performance Large technical footprint WP-API Advantages Succinct URI scheme Improved performance Small technical footprint Available in WordPress core Disadvantages Granular transactions No batch uploads Increased number of API calls What once required 2 web servers now required 12-15 servers WP-API Disadvantage Factors & Solutions Number of content types Solution: consolidate endpoints Volume of individual API calls Solution: batch processing endpoints Frequency of individual API calls Solution: page-level caching Lessons…
Enterprise API Development…Navigating The Battlefield
/

Enterprise API Development…Navigating The Battlefield

ByTim Nolte Updated on
Right now at work I’m the lead on a project to establish a new vendor API. Unfortunately there were decisions made on key specifications of how the API was to be developed before it was handed to me. Where I work there is a lot of legacy standards and so it’s challenging to introduce new technologies as a standard. I do see that there is a constant struggle between what APIs are needed internally versus externally, for B2B integrations. I’m always looking to try to balance this out whenever I can.