0

I am starting to redesign my current website project and would like to replace it by an architecture that can help me scale easily and has good performance.

Our prototype is running on a PHP Framework (CAKEPHP) + mySQL Server + 1ghz virutal server WIN2008 Server (feasibility test).

This system will not go online since it would not be able to meet the requirements.

  • Should be able to handle LOTS of HTTP-Requests per second ( scalability via hadoop maybe ? ) may become a bottleneck.
  • Should be able to handle many simultaneous uploads per minute ( mediafiles ) on the filesystem read and write + Media conversion ( Atm something like LAME encoder, are there faster tools? ) => bottleneck
  • Database gets many QUERIES per second ( somehow using clustering SQL Cluster or any cheaper product available? )
  • USE of CDN for static mediafiles
  • UNIX System?
  • should file compression be used ? CPU vs Bandwidth cost?

The scary part are the HTTP Requests and mediaupload & converter.

I started researching on www.highscalability.com for some good ebooks and would appreciate if some pro´s out here could give me some advice on this our helpful links.

zer02
  • 3,963
  • 4
  • 31
  • 66

2 Answers2

0
  1. use Linux as Centos, debian no windows
  2. use Pseudo-static
  3. use cache
  4. if the Browsing speed is not fast you should need CDN
  5. if you have enough money more CPUs are perfect
  6. you can use some Traffic monitoring software to judge wheather need more Bandwidth or not
nomaka
  • 58
  • 5
0

You could take a look at those books:

For media conversions you could try node.js: http://www.benfarrell.com/2012/06/14/morph-your-media-with-node-js/.

There are a few conversion(?) libraries at github: http://github.com/TooTallNate/node-lame

Perhaps a few Servers with gearman installed could handle the conversion as well.

Community
  • 1
  • 1
chris
  • 1,245
  • 1
  • 10
  • 22