This is definitely on the more technical side, but Thomas Griffin shares his approach to creating a more scalable approach for creating custom endpoints for consumable web APIs.
As WordPress continues to evolve into an application platform, it is being used more and more frequently as the backend to power APIs (REST and (un?)REST alike). You can clearly see this by all the initiative and excitement around the new JSON API that will make it into WordPress at some point in the future. I am excited about where this is headed because it means WordPress can easily be used to power web applications with consumable APIs, but since I am always concerned about performance, this post has come to life.
With the method Thomas uses in his example, he was able to reduce request times from 800ms to 110ms. If you’re creating a consumable web API with WordPress, you’ll want to read the rest.