3 ms·
I run an app with 1m+ DAU. For me, the server tech stack did not matter. What did matter was the ability to iterate quickly and identify bottlenecks. Although i
by speedyapoc 9y ago
I run an app with 1m+ DAU. For me, the server tech stack did not matter. What did matter was the ability to iterate quickly and identify bottlenecks. Although it was still critical, the server was not a massive component of the overall business, which may have given me better mileage than other users with a sub-par tech stack.
I originally started the server component using procedural PHP on $5/month shared hosting, which ground to a halt after receiving local news exposure. As users grew, I slowly built up the server stack to be more robust, tested, etc. For the most part, my users were okay with these growing pains (certain parts of the service had downtime as it expanded and grew) and they did not impact the overall success of the app.
When starting a new product, my biggest focus would be to put together the stack in a way which allows for the ability to expand, pivot, and change to account for unforeseen events. I feel that in a lot of cases, too much time is wasted debating tech stack factors which ultimately do not matter.
- superasn 9y agoYes you are 100% correct. For my last site I used a deadly combination of PHP and Perl (yes really CGI.pm) with Bootstrap3 and that site is still making good income. For my next project I had this insane idea to hunt for the best Tech/framework and I haven't gotten much done in the last 2 years. Though I think I have mastered everything from Docker to node to Lambda in the meantime. Going back to laravel/vue again. Just wanted to confirm my suspicions. I think I'm sticking to what works even though how outdated or ugly it is.