As an internet startup, at what point does PHP start to bottleneck you?
As an internet startup, at what point does your MVP build on PHP/MySql start to bottleneck you - and you absolutely need to add more layers to the technology stack in the backend?
4 comments
[ 2.8 ms ] story [ 20.6 ms ] threadThis basically caused us to not use the framework in specific areas to maximize performance, and use a network layer cache to prevent booting up the framework entirely.
As with most web tech, the main issues revolved around our database scale, we had to switch to multi-master around 2012 and it was a huge pain in the ass, also database migrations causing multi hour replica lag...
Honestly with modern cloud infra, auto scaling groups or serverless, I would have no concerns scaling PHP.
The way I always put it to anyone asking this kind of question: Build an app that scales that large and then hire someone else to deal with it :)
Man there's a lot of hate speech against PHP out there - I've been doing my research to find out what happens after the first MVP is built and successfully operational in PHP, and your answer pretty much nailed it.