In case you have a real large project with millions of users and millions of pages, you will have billions of requests to your application. This is the point where you don't have to think about the "framework" or "technology" your are using in the backend, because they are all the same: Some of them are faster, some of them can handle more "users" at once, and some of them can easily maintained by other developers.

Let's take Facebook for example, they have choosen the worst "technology ever": PHP. Most developers will tell you that you can not create any working application with this scripting language, and they will tell you how brilliant this-or-that technology is. But in fact, it does work, because the only problem you will have with PHP that you need more resources (aka Servers) instead of coding everything in C++.

But is this really interessting*? FB has more then 180.000 servers running for 1 Billion users. Let's divide this amount by 1000, and you have 180 Servers left for your application you would need fit your requirements. If you are lucky enough to implement your application in the best "framework/technology ever", you still have to run more then 100 servers at once (you need load balancers, replicators for your db's etc).

In short, you need to think about your architecture of your application, because you should always able to switch: A new data storage layer,  a new front-end framework, a new back-end framework. You need developers and administrators which are able to work with your choosen technology.

And you must split up your processes: For example, it is a bad idea to send an email directly when clicking a button in the front-end - create a database entry to send a new mail, and let a background task process the mail. This allows you to scale the required resources and won't block any processes.

That's why I have coosen PHP and the Yii-Framework for my current project cyccle.net

I can always change the MySQL Databases in the backend, can change the front-end framework, can change the backend if required (Lighttp instead of Apache, node.js instead PHP, etc.).

Hope this helps you a little bit...

Regards

Sven

http://blog.hasselba.ch

*: Yes, that's why FB implements a PHP compiler to reduce the amount of required servers. But they still use the same technology.

Hello Sven,

Thank you for your answer. Since, you have shared your views for PHP, I would like to ask a few things(this might be slightly deviated from my original question).

So, well, you mention the use of Yii framework for development but then again there are many such frameworks say, Laravel, Symfony or Codeigniter. The concept behind each of it maybe same with some features here and there. But, then is it a good idea to work with a framework?(I am already using Laravel for development currently but still wanted to hear some generic views).

Well, I have heard this from a few people that PHP is a bad scripting language and for such people Facebook is the primary example stating that even Facebook is trying to partially change its backed with powerful C and C++ code. So, my question is are such things planned? Do we really need to consider this before development?

Also, I would like to hear from someone who has developed a huge application with XPages. I have personally had a good experience with XPages but then I don't know, I am not that boosted up to work with it for huge projects. Can anyone please throw some light here too.

Regards

Sven

http://blog.hasselba.ch

*: Now means since three or four years

Thanks Sven. That really answers all of my questions. Indeed helpful.

Well, my dad handles multiple chain retail outlet and a huge wholesale business in fashion clothing here in India and have tried looking into multiple softwares (infact bought 1 from local firm out here) for stock management, billing, accounting, CRM and many more such features. I know there are many available softwares for such requirements but I was planning to build something more solid and flexible in this area (on web and not as an application).  Currently just doing some research (comparing technologies, available solutions etc.) and requirement gathering. Planning to start development next year. :)

Thanks again :)