Scotty-t.com Website Review

graphql summit 2017, keynote: “moving the new york times to graphql”. the (failing) new york times has many apps and services. some live on physical servers, others reside in the cloud™. i manage an app that runs on multiple containers orchestrated by kubernetes in (a)mazon (w)eb (s)ervices. many of our apps are migrating to (g)oogle (c)loud (p)latform. containers are great, and kubernetes is (mostly) great. “scaling” usually happens horizontally: you add more replicas of most apps at the times are adopting the 12 factor app methodology – if you haven’t been exposed, give this a read if your app doesn’t talk to the internet or a database, it will probably run lightning fast. this is not a guarantee, of course, but network latency will not be an issue. your problem would be mathematical. once you start asking the internet for data, or connect as you may have guessed, the network of sites i alluded to above is powered by wordpress™. wordpress, on its best day, is a large amount of php 5.2 code that hints at caching and queries a database whose schema i would generously call less than ideal. wp does not promise you fast queries, but it does cache data in a non-persistent fashion out of the box. what does this mean? it sets a global variable called before we go any further, let me say this: it is basically mandatory that you use persistent caching. keep in mind: you haven’t written any code yet – you have only installed wp. many of us do this and think we are magically done. we are not. if you are a simple blog that gets very little traffic: you are probably ok to move on and let your hosting company do all of the when it comes to dealing with the internals of wordpress in regards to database queries, there is not a lot you can do to speed things up. the queries are already written in a lowest common denominator way against a schema which is unforgiving. wp laces caching where it can, and simple object retrieval works as expected. wordpress does not cache queries, what it does is limit complex queries to only return