The main backend is written in php, but working with sockets is Node.JS.
if you do part with NodeJS, I suggest for just it and to take, it may be easier than PHP + NodeJs
- About architecture a lot of thought, but that's how most correctly to organize it, this is a problem.
and what thoughts?
- Was thinking about MVC, I think for this type of task, this pattern is not very suitable.
why not appropriate?
Well, if MVC is not suitable, build on HMVC.
- in order "not to grab his head."
This is why you now have a good think about it, I do not think that the toaster you someone will make the architecture of the project.
But seriously, you have town portal, i.e. the ceiling - 100k active users.
Take any cms and on its base do everything if click NodeJs - you can take a keystonejs