WordPress on Heroku
github.com
github.com
- Host all content via CDNs, which is dynamically managed via backend servers (see
below).
- Allow user interactivity via events being pushed to pub/sub event servers. On the
other side, in other DCs entirely, are the more traditional servers
which await said events. Said events are processed, aggregated, and then pushed back
up, via CDN APIs, to the CDN servers.
- Use eventual consistency concepts to simulate real-time interactivity for users.
For instance, when a user posts a review/comment we show it client-side to them,
knowing that the CDN update should be coming momentarily.
Besides the pub/sub servers, servers can be housed just about anywhere across the globe (latency isn't a huge issue any longer). If you are based in the US, you might be surprised to find out just how competitive/cheap the European market is for servers. Previously, it would have been insane to consider them, but now we can leverage them for a large reduction in costs. For example, compare Rackspace dedicated servers to OVH dedicated servers. It is roughly one order of magnitude less costly.https://atharwat.wordpress.com/2014/07/26/wordpress-on-termi...
That's one of the major reasons I run most of my WP sites on a managed service - I'm a bit too busy to keep on top of all the updates that come out.
If your site is visited enough to require non-trivial optimization, then 30 dollars a month is probably the least of your worries.