MAPS (Multi Adapter and Protocol Standards) Messaging Server addresses the complexities of IoT communication by supporting a wide range of protocols, ensuring compatibility and future-proof integration.

Wire protocol standardization has promised interoperability and flexibility in IoT messaging. However, with the evolution of protocols, achieving this seamless interoperability has become challenging. MAPS Messaging Server bridges this gap by providing comprehensive support for multiple protocols and their versions, thus facilitating a unified messaging fabric.

• Wide Protocol Support: For a full list, see supported protocol versions.
• Inter-Server Communication: Directly publish or subscribe to data on other messaging servers. Learn more.
• Advanced Filtering: Utilize JMS Selector for fine-grained message control.
• Extensibility: Easily integrate new or proprietary protocols.
• Payload Transformation: Configurable translations, such as XML to JSON.
• Namespace Partitioning: Distinct namespaces for users and groups to enhance security.
• Comprehensive Management: JMX, JMX - RestAPI via Jolokia, and web-based management with hawtio.
• RestAPI Management: Simple interface to manage connections, destinations, and schemas.

• Schema Repository: Centralized management for data integrity and format consistency. More info.
• Direct Device Integration: Offers direct communication with I2C, 1-Wire, and SPI devices, mapping interactions to topic namespaces. More info
• Versatile Authentication: Supports a variety of mechanisms, including .htpasswd, LDAP, JWT, Auth0, and more. More info
• Cloud-Native Event Storage: Event data at rest can be pushed to S3 buckets for long-term storage. More info
• Event Filtering: Advanced filtering between MAPS-servers or other servers with filtering capabilities, ensuring only relevant data is transmitted. More info
• Robust Logging: Utilizes Logback for comprehensive and customizable logging configurations. More info
• Non-Blocking Async Engine: Employs a highly efficient, non-blocking asynchronous engine and network layers, ensuring minimal locking and maximal concurrency for superior performance. Learn more.
• LoRa Support: Native support for LoRa devices, enabling direct communication without requiring a LoRaWAN network.
• Semtech Gateway Compatibility: Acts as a LoRaWAN gateway in conjunction with Semtech's technology, expanding the server's IoT ecosystem.
• mDNS Discovery: Provides service discovery via mDNS, with future enhancements planned for automatic connection and namespace/schema propagation.
• Security Domains: Configurable security domains allow for tailored authentication and authorization on a per-adapter/protocol basis.
• Flexible Configuration: Supports configuration through both Consul and file-based setups, catering to various deployment environments.

This example demonstrates a simple publish/subscribe scenario using the MQTT protocol.

Make sure the server is running and listening for MQTT connections on port 1883 (default for MQTT).

// Java-based pseudocode for an MQTT producer
MqttClient producer = new MqttClient("tcp://localhost:1883", "producer");
producer.connect();
MqttMessage message = new MqttMessage("Hello, World!".getBytes());
producer.publish("test/topic", message);
producer.disconnect();

// Java-based pseudocode for an MQTT consumer
MqttClient consumer = new MqttClient("tcp://localhost:1883", "consumer");
consumer.connect();
consumer.subscribe("test/topic");
consumer.setMessageCallback((topic, msg) -> System.out.println(new String(msg.getPayload())));
// Keep the consumer running to listen for messages

Replace localhost with the server's IP address if running remotely. Ensure the topic names match in both producer and consumer.

We welcome contributions! Please refer to our contribution guidelines for how you can participate in making MAPS Messaging Server even better.

The Maps Messaging Server is dual-licensed under the Mozilla Public License Version 2.0 (MPL 2.0) and the Apache License 2.0 with Commons Clause License Condition v1.0.

Under the MPL 2.0 license, the software is provided for use, modification, and distribution under the terms of the MPL 2.0.

Additionally, the "Commons Clause" restricts the selling of the software, which means you may not sell the software or services whose value derives entirely or substantially from the software's functionality.

For full license terms, see the LICENSE file in the repository.