Skip to Main Content
Feature Request FR-4183
Product Area Developer Experience
Status CLOSED

2 Voters

Native Integration of NATS and MQTT in ORDS for Real-Time Components in Oracle APEX

danieldiaz288 Public
· Jan 6 2025

Idea Summary
Provide native integration of NATS and MQTT in Oracle REST Data Services (ORDS) so that Oracle APEX and PL/SQL can interact in real-time with events, notifications, and messages published in these messaging systems. This would enable APEX applications to handle live events without relying solely on external WebSockets or custom solutions.

Use Case
  1. Real-Time Notifications: Allow APEX applications to receive and send real-time events without requiring constant database polling.

2. Asynchronous Event Processing: Facilitate event-driven processes without overloading the database with frequent queries.

3. IoT and Distributed System Integration: Improve communication between IoT devices and APEX via MQTT.

4. Multi-User Collaboration Applications: Instantly synchronize data in dashboards, chats, and other collaborative functionalities.

5. Business Process Automation: Trigger events in APEX based on database changes without the need for scheduled jobs.

Preferred Solution (Optional)
This could be implemented as follows:

ORDS Extension to handle message subscription and publication in NATS and MQTT from PL/SQL.

PL/SQL Procedures to interact with message queues, allowing developers to use these features declaratively.

APEX Events that react to messages published in these messaging systems to update components live without requiring custom WebSockets.

Support for Oracle Database Notifications, integrating NATS and MQTT with native database events.

Benefits

Reduced Database Load by eliminating unnecessary polling.

Improved User Experience with real-time updates in applications.

Greater Flexibility for integrations with other systems and IoT devices.

Simplified Implementation of real-time solutions in Oracle APEX.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is unlikely to make its way into APEX.

Comments

Comments

  • allam.sudhakara OP 5 months ago

    This is highly essential feature for all relational systems for integration of Enterprise IoT backbone. I believe all relational systems vendors should get united for defining and creating IoT hub definition so that all customers could really go to next state of their systems.