What are the pros and cons of using RMI or JMS between websites and business layers?

For a typical Web client -to-Servlet / WS -to-Business Tier (Spring or EJB) application, what are the tradeoffs of approaches such as remote RPC or messaging for the Web layer (Servlet) for the remote business layer, in addition to the basic aspects of synchronization / asynchrony?

+3
source share
3 answers

By web client, do you mean web browser? If my views on things like DWR or JAX-RS are my recommendations. RMI or JMS really work when both sides are Java code.

, , , , -. / RMI JMS API -.

- POJO Java, , Spring Remoting , , RMI JMS - , -, ( - -).

, . Spring Remoting, , RMI, JMS HTTP, , XMPP - URI.

+3

RMI Spring , . , .

+1

SUN RMI .

. , . JMS, , gc, RMI . , System.gc() , .

RMI JDK 6 , JHC - . RMI nio sun.nio system.gc().

- () . RPC , . JMS , .

0

Source: https://habr.com/ru/post/1696945/


All Articles