0

Our application is growing fast so now we need to scale the infrastructure to don't slow down the entire website without worrying on how many users we have

The backend system is based on many curl calls lasting 1-10 seconds and they need to be executed in parallel

We currently have a 4GB ram 4 core vps but sometime we get 503 error when all the 50 channels start in parallel (we setup 50 cron job) that execute 5 curl call/each

These numbers are going to increment fast so we need to find a solution to don't let the end user wait more than a minute to get his things done

Do we need a dedicated server, or it won't make much difference? Or set up aws lambda functions with sns queue? Amazon would be the best solution because whatever amount of sns messages we put in the queue and instantly they will get processed by enabling the trigger, but the lambda function currently don't support PHP so we would to rewrite all the code in Python

How would you manage this situation to improve the performance?

lorigio
  • 11
  • 2
  • Why PHP, curl and Python? – Michael Hampton Feb 25 '17 at 20:56
  • 1
    I'm not sure if your problem is the kind of [capacity planning and sizing problem](http://serverfault.com/q/350454/37681) that our Q&A platform can't solve for you but which you need to determine yourself. Also when you look at the real life architectures on the http://highscalability.com/ blog you'll notice that it is not unusual to rethink both your application and infra design and implementation choices when dealing with aggressive scale ups, so don't dismiss that thought. – HBruijn Feb 25 '17 at 20:56
  • Please do not post duplicate questions. – EEAA Feb 25 '17 at 21:14

0 Answers0