Technical Architect
A Christ-follower, husband, father, and WordPress Developer with Forum One.
Similar Posts
Development / Geek / Links / Programming
The Road Of Lifelong Learning To Be A Better Developer – Using Git Better
As a developer and, in some areas, a perfectionist I’m always after better #development practices when working collaboratively. An I personally find value in the #commit history. As a #git user I appreciate detailed case from @ecampidoglio on the proper way to keep a clean commit history. The Case for Pull Rebase
WordCamp GR 2017 – WP-API: The Good, the Bad, and the Ugly – J Andrew Scott
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…