Skip to main content
Software Engineering

Return to Question

Post Reopened by maple_shaft♦
Tried to improve question by removing unnecessary opinion fishing and clarifying the question.
Source Link
maple_shaft ♦
maple_shaft ♦
  • 26.6k
  • 12
  • 60
  • 136

Does What risks are there to using Node.js with Java EE most effectively fulfill our software requirements?

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is tomcatTomcat to implement REST services for serving back-end.

But I think it will add an unnecessary overhead if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed inAm I wrong to consider these risks with such an Architectural decision? What would be the organizations.potential rationale for deciding on using two completely different frameworks like this where there is functionality and feature overlap?

Does using Node.js with Java EE most effectively fulfill our software requirements?

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think it will add an unnecessary overhead if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed in the organizations.

What risks are there to using Node.js with Java EE?

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is Tomcat to implement REST services for serving back-end.

I think it will add an unnecessary overhead if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Am I wrong to consider these risks with such an Architectural decision? What would be the potential rationale for deciding on using two completely different frameworks like this where there is functionality and feature overlap?

edited title
Source Link
smali
smali
  • 119
  • 7

Is it a good practice to use Does using Node.js along with Java EE most effectively fulfill our software requirements?

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think its not a good practiceit will add an unnecessary overhead if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed in the organizations.

Is it a good practice to use Node.js along with Java EE

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think its not a good practice if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed in the organizations.

Does using Node.js with Java EE most effectively fulfill our software requirements?

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think it will add an unnecessary overhead if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed in the organizations.

Post Closed as "Opinion-based" by gnat, Kilian Foth, Robert Harvey, Philipp, Thomas Owens♦
list instead of code
Source Link
edit approved Apr 12, 2017 at 9:36
Randy
edit approved Apr 12, 2017 at 9:36
Randy
  • 145
  • 7

We are developing a B2B web application in which we are using(suggested by seniors) two server oneservers. One is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think its not a good practice if we consider the following point.:

-Need to maintain two servers.
-Security(Session management/View Management).
-Resources (need Node.js developers as well as Java Developers).
-Deployment and Configurations.
  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed in the organizations.

We are developing a B2B web application in which we are using(suggested by seniors) two server one is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think its not a good practice if we consider the following point.

-Need to maintain two servers.
-Security(Session management/View Management).
-Resources (need Node.js developers as well as Java Developers).
-Deployment and Configurations.

Or is a common practice being followed in the organizations.

We are developing a B2B web application in which we are using(suggested by seniors) two servers. One is Node.js (to serve all the request related html & static content) and the other is tomcat to implement REST services for serving back-end.

But I think its not a good practice if we consider the following:

  • Need to maintain two servers.
  • Security(Session management/View Management).
  • Resources (need Node.js developers as well as Java Developers).
  • Deployment and Configurations.

Or is a common practice being followed in the organizations.

Source Link
smali
smali
  • 119
  • 7