All Classes and Interfaces
Class
Description
Messenger abstract class to send messages across channels using a
This class doesn't offer any abstract method making it usable as plain object, but it's suggested to extend it and override
Broker.This class doesn't offer any abstract method making it usable as plain object, but it's suggested to extend it and override
AbstractMessenger.loadBroker() if
you want your own implementation.ActiveMQ broker implementation to send data using topic producers and consumers.
Represents an object that can transfer byte-array data across channels.
In popular terms, this is a globalized producer that deliver/publish temporary data to multiple consumers using topics or queues (depending on the implementation) and can also consume the data itself by subscribing to channels.
In popular terms, this is a globalized producer that deliver/publish temporary data to multiple consumers using topics or queues (depending on the implementation) and can also consume the data itself by subscribing to channels.
Byte codec interface to encode and decode bytes into desired object.
Represents and operation that accept a channel name and the data produced by the channel.
Unlike
Unlike
Consumer, this operation can throw an IOException.Minimalist interface which provides a
This implementation can also provide information about connection state.
Connection.This implementation can also provide information about connection state.
An object to generate and identify messages with a unique id.
A 32-bit data identifier that generates unique integer ids.
A 64-bit data identifier that generates unique long ids.
Encryptor interface to encrypt and decrypt any provided String.
By default, this is just a bridge to regular Java Cipher usage.
By default, this is just a bridge to regular Java Cipher usage.
Sql broker implementation that use hikari library to make connections to database.
The operations are the same as sql broker, it just made any connection with hikari library.
The operations are the same as sql broker, it just made any connection with hikari library.
Redis broker implementation to send data via publish and subscriptions.
This kind of broker will encode any byte array as String and viceversa.
Some operations made in this instance can fail due authentication errors, so it requires the password as well.
This kind of broker will encode any byte array as String and viceversa.
Some operations made in this instance can fail due authentication errors, so it requires the password as well.
Bridge class to detect received messages from Redis database.
Kafka broker implementation to publish and consumer using empty-keys records.
Take in count that any producer and consumer used in this instance should be compatible with byte array values.
Take in count that any producer and consumer used in this instance should be compatible with byte array values.
Redis broker implementation to send data via publish and subscriptions.
This kind of broker will encode any byte array as String and viceversa.
Some operations made in this instance can fail due authentication errors, so it requires the password as well.
This kind of broker will encode any byte array as String and viceversa.
Some operations made in this instance can fail due authentication errors, so it requires the password as well.
Bridge class to detect received messages from Redis database.
A minimalist representation of a Logger implementation with a small amount of logging levels.
Unlike normal logger implementations, this one uses numbers as levels:
1 = ERROR / SEVERE
2 = WARNING
3 = INFO
4 = DEBUG INFORMATION
Unlike normal logger implementations, this one uses numbers as levels:
1 = ERROR / SEVERE
2 = WARNING
3 = INFO
4 = DEBUG INFORMATION
Java Util Logging implementation of LogFilter.
Log4j2 implementation of LogFilter.
SLF4J implementation of LogFilter.
An object to consume channel messages.
This object can also provide an
This object can also provide an
Encryptor to make a secure message delivery.NATS broker implementation to publish data and consume it with subject subscription.
Represents a Broker implementation that send and receive plain-text data
using a specified byte codec to convert byte arrays into/from String.
PostgreSQL broker implementation to send data using
Is this scalable?
No
Allows large messages?
No
Should I use it?
Maybe
LISTEN and NOTIFY statements.Is this scalable?
No
Allows large messages?
No
Should I use it?
Maybe
PostgreSQL broker implementation that use hikari library to make connections to database.
The operations are the same as PostgreSQL broker, it just made any connection with hikari library.
The operations are the same as PostgreSQL broker, it just made any connection with hikari library.
RabbitMQ broker implementation to send data using queue and consumer via exchange.
Sql broker implementation to send data via polling.
Take in count that this is not a real broker, can be used as one but the client is doing all the job via insertion and repeatable deletion.
Take in count that this is not a real broker, can be used as one but the client is doing all the job via insertion and repeatable deletion.
An object that executes submitted Runnable tasks and return itself as cancellable objects.
Unlike
Unlike
Executor, this kind of object allows to execute delayed and repeatable tasks.Valkey broker implementation to send data via publish and subscriptions.
This kind of broker will encode any byte array as String and viceversa.
Some operations made in this instance can fail due authentication errors, so it requires the password as well.
This kind of broker will encode any byte array as String and viceversa.
Some operations made in this instance can fail due authentication errors, so it requires the password as well.
Bridge class to detect received messages from Valkey database.
A Java implementation of the Z85 encoding scheme, based on the Z85 specification used by ZeroMQ,
which is derivative of Ascii85 (and part of the Base85 family) encoding mechanism, but focused on source code usability.
This implementation contains the following types of encoding and decoding: Default
This implementation contains the following types of encoding and decoding: Default
This class provides methods to decode Z85 encoded Strings into byte arrays.
This class provides methods to encode byte arrays into Z85 encoded Strings.