Distributed Architecture in J2EE (Distributed Architecture in J2EE)
Just in the Huihoo forum, I saw an article how to improve the efficiency of JBoss RMI / IIOP. "There is an application is the client Swing J2EE Server, running in the intranet, there is no problem. There is a customer, many branches They are all connected to the headquarters through ADSL (2M bandwidth). J2EE server is put on headquarters, feels particularly slow ", I haven't found a solution. Just watching an article "eBays J2EE Backend Serving over 400 Million Transactions" http://www.theserverside.com/news/thread.jsp?thread_id=2015555555555555555555555555555555555555555388888888888883883375 Support such a big throughput, indeed amazing.
There is an idea that is the idea of thinking, distributed system. Currently, in the database system, many people's thinking is also focused on database performance, how to use private database languages, how to use stored procedures, and even some forum software direct database layers, these are simple "down thinking" , Do the alive, this thinking is actually behind. Use cache Cache, multiple distributed cache, place database data in memory, and both the database's database operation versatility, not for specific database products, but also have expandability and scalability. This is a new upward thinking, performance improvement direction. http://www.theserverside.com/resources/article.jsp?l=db_break
These J2EE performance adjustments have how to achieve distributed applications, and now I still have some advanced applications, I plan to be placed on one side first, and then come back to study.
The above figure perfect explanation of the principle of the existing step-by-step application of J2EE.
In the third step, when the reference is obtained, it is already transparent to the client using Remote Object and the local.
There are many Naming Services now, the most common is DNS, which is the domain name interpreter we usually used. There are also: RMI (Java special), Cobra, LDAP, NIS, etc. JBoss is using RMI as its Naming Services.
Article quotes: "Serialization and Deserization Are the Same as Marshalling and UNMARSHALLING for Those Familiar with RPC Terminology.".
Java Naming Directory Interface (JNDI) Architecture
J2EE uses JNDI's API access. After these APIs, the call to the name service is relatively transparent, and the name service application is nothing else.
