java - Usability: How do I provide & easily deploy a (preferably node.js + MongoDB based) server backend for my users? -

i'm planing application (brainstorming, more or less), designed used in small organizations. app require syncronization w/ backend-server, e.g. user management , advanced, centralized functionality. server has hosted locally , should able run on linux, mac , windows. haven't decided how i'm going realize this, don't know smartest approach.

technically speaking, interessting approach seemed node.js + mongoose, connecting local mongodb. i'm struggeling: how ensure it's easy , convienient organization's set up?

installing node.js + mongodb tedious work , far standartized , easy. don't have ressources provide detailled walthrough every major os , configuration or take on setup myself. ideally, local administrator should run sort of setup on machine used server (a "regular" pc running 24/7 should suffice) , have system , running, similar way games provide executables hosting small game-servers couple friends (minecraft, instance).

i thought java ee, though haven't dug details here. i'm unsure whether option.

many people suggest outsource backend (baas), e.g. parse.com or similar services. not option, since it's mandatory backend hosted locally.

i'm sorry if question unspecific, unfortunately, don't know start.

i can give advice both sysadmin's side , developers side.

sysadmin

setting node.js not big task. setting mongodb correctly is. not business application vendor, not when 1 man show foss project, assume. administrators task set database, let him it. tell them need, maybe point out security concerns , capable sysadmin his job , set environment.

there things underestimate, however.

applications, useful ones, tend used. mongodb has many benefits, being polite resources isn't 1 of them. running on surplus pc may work in software development company or visual effects company, every workstation has big mem, in accountant company application lack resources quite fast. not make promises "will run on surplus desktop" until absolutely, positively sure because did extensive load tests make sure right. sensible sysadmin monitor application anyway , scale resources when necessary. when make such promises , break them, loose single important factor software: users trust. once loose it, very hard back.

developer

you have decide whether mongodb right tool job. have relations between documents, in change of of document has reflected in others, have really careful. ask if decision based on rational, educated basis. have seen projects been implemented nosql databases have been way better of relational database, because nosql sort of everybody's darling.

it far way node.js java ee. concepts of java ee not easy grasp, if have little experience in application development in general , java.

the problem

without knowing application, hard make suggestion or give advice. why has mongodb local? can't done vpc? webapp, desktop app or server app? can source ode disclosed or not? how many concurrent users per installation can expected? want modular or monolithic app? communication needs? experience in programming languages? want accomplish , services want provide app.