What to choose for a high-load site?

Question

CMS

A site with a high load is planned.
From the functionality - registration of users with different rights, a huge amount of content with different categories, filters, tags, etc., communication of people through the site. In general, everything is pretty standard, but it needs to work quickly, as a large load is planned.
Personally, I have no experience in writing this kind of thing, but it so happened that I will have to acquire this experience in the near future.
What can you recommend? The question is quite broad and can include anything: what framework / CMS / PL, what database, design patterns, software, server configuration, etc. etc. It would be great if someone could share their actual experience of building something like this.

Answer 1

Hire people who have this experience.

Answer 2

You have "premature optimization".

Answer 3

@mr_T What don't you like. rowdyro gave perhaps the most practical advice. You are about to write a highly stressed project without any experience. What do you think will come out of this? In the end, you still have to hire professionals who will rewrite everything. You will only lose time and money.
But if you are all set to do it yourself, I could recommend the following: nodejs for webmord, for user communication - its own or erlang. I would do all the heavy nasty calculations in java/scala - easy to learn and fast. It’s not specific to say about the database, but I would take postgres. Although many advise for the nosql node.
Well, if there is no doing to teach the whole zoo - take a node and write on it. And most importantly, do not suffer from premature optimization, but at the same time do not forget about scalability.
But it is better, krnechno, to entrust it to professionals.

Answer 4

I advise you to use yii framework

Answer 5

Judging by the context, someone decided to write another Facebook clone that crowds of people rush to and you need to think about loads in advance, right? ) My advice - write on what you know better because the project will not take off anyway.
And the load should be given specific numbers. For example: stable 300 rps, page generation time is no more than 0.1 sec, the norm is 0.02 sec. Next, metrics are set depending on the characteristics of the project. 100 items, for example.

Answer 6

1. Find, after all, people :)
2. If you have to do it yourself - make a prototype. If it takes off, take people to do for the highload.
3. Find out if a highload is really expected. Maybe with what you consider a highload, a simple system can actually handle it.
4. If you still have a highload and you still need to immediately and still without people - figure out the meaning of the word "scalability". And to understand that the words "loaded" and "fast" are completely unrelated in this context. And platforms, languages ​​and databases are completely secondary.