What is the best way to organize the project structure (Server, database, clients)?

Question

Software design

It is necessary to make a project in which there should be: Server, DB, Website, Mobile clients.
The question is this: Is it possible to write a nodejs server with an API and a database, and it will also render the site. Mobile applications will also access this API. Or you need to make a separate server with a database and a website with a backend. Will the backend site access the server like mobile apps?
Roughly speaking, there will be two tables in the database (users and addresses). And Which is better to use: MongoDB or PostgresQL.
And is it worth making a server in NodeJS or writing in JAVA ..?

Answer 1

Without a specific statement of the problem - it makes no sense.
Well, yes, in the general case, the server, database, mobile clients. So what?
Maybe your task allows you to simplify your life somewhere and do without some element.
Or maybe, on the contrary, the task will also require caching and clustering / sharding ....
But without setting a task (TK), this is not visible.
And Which is better to use: MongoDB or PostgresQL.
And is it worth making a server in NodeJS or writing in JAVA ..?
It's as simple as that: use what you personally (or the developer you hired) knows best.

Answer 2

Agree with InoMono
I generally prefer PostgreSQL for its versatility: you can work with both relational data and MongoDB-style documents.
Plus PostgREST as an API: I get a ready-made REST API to the database, which is universally used for web applications and mobile clients.