Offloading services from WordPress to outer services
summary
Argues that heavy tasks like search, ranking, logging, backups and sorting must move out of WordPress into external services via connector plugins calling microservices over APIs; examples include using Google Analytics for popular-post ranking, ElasticSearch for fuzzy full‑text and metadata queries, and CloudFront CDN + Amazon S3/RDS for HTML, assets and durable DB storage. Claims this reduces DB row growth, keeps costs low, and shares open‑source configs, plugins and automation that actually run at scale.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:17Overview
- 3:00Basic idea
- 4:10Connector plugins
- 4:54Akismet plugin
- 6:41Kaseys plugin
- 8:14Google Analytics plugin
- 9:31Related posts plugin
- 11:24Elasticsearch plugin
- 14:04Caching plugin
- 16:08AWS Map
- 19:31Building microservices
- 19:44microservices
- 20:14services model
- 21:56conclusion
related talks
42mMicroservices – The FAAS and the Furious
20mMicroservices in the future
51mAvoiding Microservice Megadisasters
45mAvoiding Microservice Megadisasters
51mScaling Wix with microservices architecture
01h 00mService Oriented Architecture for Robust & Scalable Systems
35mChopping the monolith
24mMicroservices in Practice