I’m estimating the costing of a scalable streaming platform, with a user base that is expected to grow to 100,000 within 2 years of launch.
My first thought was building with scale in mind. I know WP will start to struggle if this isn’t executed properly. I’ve researched all the elements I thought could be problemematic, and come to this plan - roughly how many concurrent users would this be able to handle?
CRM
Fully custom highly optimised WordPress theme.
Hosting
Kinsta or WP engine for their cloud based database databasing and caching capabilities.
Video Streaming
Video content stored on Google cloud and streamed with a video.js player (AJAX calls token every 5 mins for authentication) to offload processing/bandwidth with high amounts of concurrent users.
**…
I’m estimating the costing of a scalable streaming platform, with a user base that is expected to grow to 100,000 within 2 years of launch.
My first thought was building with scale in mind. I know WP will start to struggle if this isn’t executed properly. I’ve researched all the elements I thought could be problemematic, and come to this plan - roughly how many concurrent users would this be able to handle?
CRM
Fully custom highly optimised WordPress theme.
Hosting
Kinsta or WP engine for their cloud based database databasing and caching capabilities.
Video Streaming
Video content stored on Google cloud and streamed with a video.js player (AJAX calls token every 5 mins for authentication) to offload processing/bandwidth with high amounts of concurrent users.
Subscription system
Offload subscription payments to Stripe subscriptions API to ease the load on the DB.
Comment System
Default WP comment system with custom coding to allow only admins to reply to comments. Originally I thought this would be a problem at scale, but I think using WP Engine/Kinsta would mitigate this?