java - Using webservices to connect front-end and back-end, a good idea? -


This project runs front-end web server on one JVM and back-end on the other. To call the web any biz-logic methods in the back-end, it has to call the web service (Jax-WS).

I understand that parts of the application will need to be integrated with other systems, it is a good idea to distribute a service through the web server service, but I do not have a system yet Where is the every biz-logic call highlighted as a webmaster

Display? transaction? Generally a good idea?

I'm a big fan of what theory (keep it simple). There should be compelling reason to split the application between JVM and make the WS interface layer. Potential reasons include the need to measure the presentation level different from the business level. JVM tuning differences, such as a different garbage collection algorithm Or DMZ is needed.

If no compelling reason exists, then combines the isolated complexity which may cause headache for development from the development.

Need to highlight the business and the argument for other applications does not represent the reason for dividing the level between JVMs. Business logic still comes out through WS for external applications While your presentation level is physically in the same GVM and directly references the business level through the POJO implementation of professional service. While there will be a web service cover around the POO implementation, exposing business services as web services.


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -