Hi!
Bad (and maybe long, confused) English here, too ;-)
Well, I have no experience in the kind of site you mentioned. I'm a C#/Java developer, with Node.js experience. Some personal comments:
- Search will depend on the concurrency query support of your database (unless you prepare an in-memory implementation, but in Node.js you must remember you have only one thread for JavaScript to run things). The bottleneck will be your database, and Node.js async I/O capabilities will derive all the work to the database engine, leaving Node to attend other users
- Django/Python is a bit opinionated, and Node.js is a more "free" way of doing things. Django/Python is like the Ruby on Rails of Python, with modules and ecosystem, but with the Django-way-of-doing-things. You have the friction of Python 2.7 vs 3.x. Node.js is simple, but you have more work putting all the pieces in place. Personally, I prefer the Node.js way. Simplicity and choices. And Python still has the GIL
https://wiki.python.org/moin/GlobalInterpreterLock at least in CPython, you could try Jython (notably, Node.js avoid GIL using only one thread for JavaScript, and async I/O).
- Meteor is "too much" Meteor, that is, is the "Meteor-way-of-doing-things". Even client-side JavaScript should be obey the Meteor way. IMO, that is easy way (that is, all piece are in place), but the pieces were chose by others. Meteor has a vibrant community, but I feel you lost the vibrant client-side JavaScript community, and the choice of other options. BTW, check the meteor open sourced
with videos, like your site
Other comments?
Angel "Java" Lopez
@ajlopez