Byron Kiourtzoglou

About Byron Kiourtzoglou

Byron is a master software engineer working in the IT and Telecom domains. He is always fascinated by SOA, middleware services and mobile development. Byron is co-founder and Executive Editor at Java Code Geeks.

Messaging principals in Java applications

Messaging is a crucial aspect of every Java application, especially for applications involving Enterprise Application integration (EAI) or separation of concerns, such us multi-tier WEB applications.

Messaging can be separated in two main categories, synchronous and asynchronous. With synchronous messaging the initiator of a conversation waits for a replay to each submitted request, on the other hand, in asynchronous messaging the initiator is not interested for the replay. The most common and efficient way for Java processes to communicate in a synchronous manner is through Remote Method Invocation (RMI). Asynchronous communication is mainly implemented using Java Messaging Service (JMS).

This post presents a design pattern concerning asynchronous communication between Java processes for low latency and high throughput applications.

As mentioned above JMS is considered to be the “de facto” standard for asynchronous application messaging. Nevertheless JMS introduces a noticeable increase in latency due to internal checks and procedures involved to the message exchange life-cycle (even for in memory brokers). Our preferred way to handle asynchronous messaging for achieving low latency and high throughput is :

  • If persistence is mandatory, then the best approach is to use JMS persistent queues or topics
  • If persistence is not mandatory then you should implement asynchronous messaging as follows :
    • Message container should be a List, preferably the ArrayList implementation or a Map, preferably the HashMap Implementation
    • Sender processes should perform synchronized access, using the synchronized block, to insert messages to the container
    • Implement a pool of receiver processes that access the message container synchronously, using the synchronized block, and retract messages
    • Messages can be implemented in many flavors, our preferred method is Plain Old Java Objects (POJOs) implementing the Externalizable interface so at to manually handle the serialization process.

Do you want to know how to develop your skillset to become a Java Rockstar?

Subscribe to our newsletter to start Rocking right now!

To get you started we give you two of our best selling eBooks for FREE!

JPA Mini Book

Learn how to leverage the power of JPA in order to create robust and flexible Java applications. With this Mini Book, you will get introduced to JPA and smoothly transition to more advanced concepts.

JVM Troubleshooting Guide

The Java virtual machine is really the foundation of any Java EE platform. Learn how to master it with this advanced guide!

Given email address is already subscribed, thank you!
Oops. Something went wrong. Please try again later.
Please provide a valid email address.
Thank you, your sign-up request was successful! Please check your e-mail inbox.
Please complete the CAPTCHA.
Please fill in the required fields.

Leave a Reply


+ seven = 14



Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use | Privacy Policy
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
Do you want to know how to develop your skillset and become a ...
Java Rockstar?

Subscribe to our newsletter to start Rocking right now!

To get you started we give you two of our best selling eBooks for FREE!

Get ready to Rock!
You can download the complementary eBooks using the links below:
Close