Tutorial for building J2EE applications using JBoss and eclipse Chapter 2 Part 2

Distributed applications in J2EE (distributed architecture in J2EE)

I read an article on how to improve the efficiency of JBoss RMI/IIOP at the huihoo forum. "One application is a client swing + J2EE server and runs on the Intranet. There is now a customer with many branches connected to the Headquarters through ADSL (2 M bandwidth. The J2EE server is deployed at the headquarters, which is very slow. "I still cannot find a solution to this problem. I just read another article "eBays J2EE backend serving over 400 million transactions a day" http://www.theserverside.com/news/thread.jsp? Thread_id = 20155 & article_count = 48 eBay can use the J2EE architecture to support such a large throughput, which is indeed amazing.

There is an idea: the upward thinking, distributed applications. Currently, in database systems, many people focus on improving database performance, how to use the specialized database language, how to use stored procedures, and even some forum software to write at the database layer, these are simple "downward thinking", and they are actually falling behind. Using Cache and multiple distributed caches, you can store database data in the memory. This not only achieves the versatility of database operations for programs, but also provides scalability and scalability for specific database products. This is a new way of thinking and improving performance. Http://www.theserverside.com/resources/article.jsp? L = db_break

These J2EE performance adjustments also show how to implement distributed applications. For me, there are still some advanced applications. I plan to put them aside for the moment and wait until I lay the foundation and come back to study them.

It perfectly illustrates the principles of J2EE's existing step-by-step application.

In step 3, after obtaining the object reference, the use of remote object and local is transparent to the client.

There are many naming services. The most common one is DNS, which is the domain name interpreter we usually use. For example, RMI (for Java purposes), Cobra, LDAP, and NIS. JBoss uses Rmi as its naming services.

Quoted in the article:"Serialization and deserialization are the same as parameter alling and unmarshalling for those familiar with RPC terminology.".

Java Naming Directory Interface (JNDI) Architecture

 

J2EE uses the jndi api for access. With these APIs, the call to the name service is relatively transparent. In the future, no matter what the name service application is.