What does this mean? Are you being paid for this? What you’ve described is a massive amount of work, especially for someone who’s just learning Node, and I wonder if this is a great opportunity for you, or a way for someone else to get a project built for less than they should be paying.
As far as tech recommendations, just about anything should work. I would advise you use a relational database like Postgres or MySQL rather than a NoSQL database like Mongo as you’ll need to be referencing lots of different tables. I’ve recently worked with SequelizeJS in Node to manage a Postgres DB and found it very easy and featureful.
the basic elements of what you describe are an authentication system with a back end database tos tore preference and other resources.
You can use any stack for this. The above poster suggests an SQL db vs a NoSQL db, and i know either one will work, but don’t know if the reason he gave is a reason not to use a no SQL, I am fairly sure that large projects are using noSQL dbs also.
This is a big project with lots of building blocks and if it is for a client and it’s your first attenpt at these technologies they won’t be getting a quality product.
The back end projects in FCC cover all of the things you’d need for this project, and if you can do them, you can do the one you specified. The FCC user stories are much much simpler and you could do them, then simply chage up your labels and text and names of documents to match a job board rather than a book trade for example.
It’s not the size of the project that matters in this case, but I foresee a lot of table joins (get all Projects by User, or get all Users by Projects, or get all Projects and their Users by Project Owner, etc…) and that’s where relational databases excel. NoSQL databases have their own ways of making this sort of thing work, but then you’re not playing to the strength of the technology. So, IMO, it’s better to use a relational DB for this sort of project.
My database preferences notwithstanding, you’re not limited by technology here. Just about any stack will work, if you know how to use it. I don’t want to rain on your parade, but…
You’re setting yourself up for pain by jumping into a professional, full-stack gig like this. It would be one thing if you were subcontracted by someone who knew the ropes, but you have a lot of learning ahead of you and this is a project that I wouldn’t take on by myself. Good luck.
I don’t know your current circumstances or how well you know web dev. I assume you know quite a fair bit otherwise you won’t be able to land yourself this project. If this is true, you should already know which technology to use.
What concerns me is that you got such a large project but still debating which technology to use for front-end. My intuition tells me that you just want a quick easy solution to building a large scale project with no money down, in addition to that you just want to piece together fragment of module code and somehow connect them all altogether.
I am not too sure if this is a real project or a friendly suggest project, but I think you are jumping into extremely deep water if this is paid and you are still learning.