As others have pointed out already, there isn't really such a thing as a best framework. Many of the fundamental ideas are the same no matter what you choose, s

As others have pointed out already, there isn't really such a thing as a best framework. Many of the fundamental ideas are the same no matter what you choose, so the potential benefits of switching are meager. Stick with what you know for the parts that don't absolutely require another solution; not all (parts of) pages will be so interactive. Then branch out a bit where needed, e.g. to handle socket connections well. Maybe not all of that needs to be handled by the same service? If you move the semi-realtime stuff into a separate project, it will be a lot smaller in scope, hence less risky to experiment with. Regardless, I wouldn't stray too far. If you'll be writing Javascript anyway, NodeJS could still be fine, but don't needlessly bring in a third language. Do try Channels, but don't overlook other Python solutions. Tornado is a workhorse that doesn't get nearly enough credit in my opinion.