Alternative Datastores in WordPress
summary
WordPress stores about a dozen core tables and $wpdb becomes slow when using post_meta for structured queries, so use custom tables (create via dbDelta) for fast lookups like latitude/longitude instead of longtext meta. Use ElasticSearch with geo_point or ElasticPress for sub-100ms search results but expect eventual consistency. Use Redis or memcached as an in‑memory object cache or task queue (memcached ~1MB per item, Redis higher) and avoid stuffing WP cron’s serialized blob.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:23Talk TOC
- 2:24WP Storage
- 4:23Datastores Oversimplified
- 5:05Custom Tables/Views
- 7:53Redis/Memcached
- 10:56Geolocation - Rough Query
- 12:15Geolocation - MySQL Custom Table
- 13:02Geolocation - MySQL View
- 13:38Geolocation - Elasticsearch
- 14:25Geolocation - Redis
- 16:47Task Runner - General Concept
- 17:11Task Runner - WP
- 17:56Task Runner - MySQL
- 18:24Task Runner - Elasticsearch
- 18:39Task Runner - Redis
- 20:22Content Syndication - MySQL
- 21:43Content Syndication - Views!
- 22:38Content Syndication - Elasticsearch
- 23:41Implementation Notes
