JGroups 5.0 of the first Alpha version released , this version of the API made significant changes. The team also revealed that before the first beta release, there may be further API changes.
Here's a look at the new 5.0 features.
The biggest change is 5.0 Message (message) has now become the interface, and provides a number of message classes implement it, several are listed below:
- BytesMessage : This is an alternative to the old 4.x Message type, having a payload byte array as
- ObjectMessage : receiving a supporting object as payload
- NioMessage : having as its payload NIO ByteBuffer
- EmptyMessage : This class does not include a load, mainly for transmitting a message header only, such as heartbeat information. The main use of such internal JGroups, it's very low memory footprint
- CompositeMessage : Message used to carry other types of messages
The main advantage of this variation is the use of different message types, i.e., do not like 4.x message payload grouped as an array of bytes, the payload can now be added to the message without grouping, only the transmission network was grouped before the message. In this way saves time memory allocation.
Another advantage is that the application can register their message type, which means that we can control how messages are created, such as the use of external heap memory (off-heap memory) instead of heap memory.
Other notable changes include:
- Removing a lot of complicated things, such as some AuthToken achieve: SASL, S3_PING and GOOGLE_PING (now have a better alternative)
- The first Alpha version 8 still run under Java, but Java 11 will be the basis for the future, the team said it will use the Java language features unique 11
Click here to view a complete list of changes .
5.0 Documentation Address: http://www.jgroups.org/manual5/index.html