Want to build a social network with JS Only ; any Stack to advise me ? Why those choice ?

Angular? Node? Many options, JS frameworks are something we're not short on

@DucksCanCode what in back end & what in front end ; and what for mobiles ? #BestApproach pls

@rajilsaj it depends on you and your web app, I can't answer that. Look up Node.JS and API's, that's the only way to do it, you need some sort of storage system for a social site, and hence, you need a server where you can store and monitor files, probably a cloud server running a Node instance for your site.

We also decided once to build social site using either MEAN or MERN stack but I'm still at beginner level and I still have many doubt about it because I don't have much experience building complex sites
1. Can mongodb fit for this?
2. Is nodejs secure for this much big app?
3. Can angular handel big data in the front end(if needed and that's why I thought of React)
4. Have to think about scalability too

And I totally think its possible to make large application using JS but the code or whatever you build must be good enough in terms of coding and optimisation.
* these are just my thoughts *

@lazysnail The most important part in any large scale large user count project is to focus on what data you are going to store and how you need to search or aggregate that information.

Graph databases are designed for cases where you have lots or relations between items and need to follow that chain, for example facebooks friends of friends of friends.

Object databases excel when you have to store complex data about an item but are not necessarily good if the sub items are shared between objects.

Relational databases, like sql, are actually one of the most versatile but can need a lot of planning and aggregation for some kinds of dependencies.

If you have that part figured out you could probably get by with any framework or language for backend/frontend so pick one you comfortable with.

If it outgrows your platform you can always diversify later, breaking out performance hotpots to another solution better suited for it.

@Voxera that's the point. I totally don't know what fits where exactly as I'm still student, will be graduating in next month. And I've worked with only MySQL, Oracle, MongoDB but only small scale applications. Even I didn't got any guidance regarding to this problem and I totally think I lack experience when I've to choose among this.
I don't know if its ok that I can't differentiate them right now due to lack of experience. Or is it bad.?

@lazysnail Focus on how the users will interact and what you think they need.

Thats you goal until you have more to go on.

Then break it into tasks.

What information will be presented together, what needs dynamic updating and what can wait to page reload. Most modern social networks never reload the page but loads everything dynamically.

From there, where does the info come from, do we need to index or aggregate it to show it.

Make sure to split presentation from data retrieval so that when you need to change how data is stored or fetched you do not have to change many places. Read up on SOLID.

@Voxera m'y worries : fast system, hosting plans, high traffic, mobile app with JS too, handling chat & video calls
Storage : pics, posts,

@DucksCanCode simple Idea => sharing news hosted Else where, chat apps, videos calls and group calls, rates systems, multi-connections threads

@rajilsaj If you are going to do it just start. Some problems you just have to solve on he way and some questions will be more clear once you have some rudimentary system going.

And you always get experience.

@Voxera thank you very much for taking time to explain us all this stuff. Totally appreciate it. Will work hard.

@Voxera you're right