Realtime Server Action on an Entity
711
Views
8
Comments
New
Backend

Realtime updates actions on Database Entity, in addition to the normal read/create/update/delete actions would be great if we have listen action, this listen action will publish an event to any subscribers based on Id or on the entity list, 

what we do now to work around is as follow: 

1- Use external library  (e.g. Signalr, Websockets)

2- Timers and processes which is not true realtime.

___________________________________________________________________________________________

This proposal suggests the implementation of real-time functionality in the OutSystems platform to enable developers to build applications that can deliver instant updates to users. The proposed feature will use WebSockets to establish persistent connections between the client and server, facilitating real-time data exchange. This functionality will significantly enhance user experience, increase application interactivity, and open new possibilities for creating dynamic and responsive applications.

Problem Statement:

Currently, OutSystems primarily follows a request-response model, limiting the ability to provide real-time updates to end-users. Many modern applications require real-time capabilities, such as instant notifications, live chat, collaborative tools, and live data feeds. The absence of a native real-time solution in OutSystems creates challenges for developers who have to resort to workarounds and external integrations, leading to more complex development efforts and reduced efficiency.

Proposed Solution:

Introduce a new real-time functionality within the OutSystems platform, leveraging the WebSocket protocol for bidirectional communication between clients and servers. This functionality will enable developers to push updates from the server to connected clients instantly. OutSystems will handle the WebSocket connection management, ensuring seamless and efficient communication.

Use Cases:

Instant Notifications: Applications can deliver real-time notifications to users for critical events like status updates, messages, or alerts.

Live Chat: Implement live chat functionality that allows users to communicate in real-time.

Live Data Feeds: Display real-time data, such as stock prices, live dashboards, or tracking information.

Business Value:

Improved User Experience: Real-time updates will lead to a more engaging and interactive user experience, increasing user satisfaction and retention.

Competitive Edge: Introducing native real-time capabilities will position OutSystems as a more versatile and competitive platform in the low-code development space.

Time and Cost Savings: Built-in real-time functionality will streamline development efforts, reducing the need for external integrations and custom workarounds.

Feedback and Community Interest:

I encourage fellow OutSystems developers and community members to provide feedback and support for this proposal. Your insights and ideas will be invaluable in shaping this feature to meet the diverse needs of OutSystems users.

Many thanks,

Mohamed Medhat Gamil

Why are all ideas that are (partly)  generated using tools like chatGPT using 10 times more text than people just writing their own idea with the help of AI?

Hi @Daniel Kuhlmann , the same like Outsystems !!! if you check the generated code by Outsystems you will find that it is almost 10 times more code that you would write !!!!


How is that relevant to your idea?

My idea is super simple and quite obvious, you have initiated totally different topic "Why are all ideas that are ......" and  I was replying to your comment, you are simply trying to depreciate my effort of trying to represent my idea in a good shape with the aid of tools like AI, what you could do intern to consider the idea itself and reply with a relevant reply not opening new topic.

Anyway, I the original idea in the first couple of lines, however; I found it more appropriate to make use of AI to formulate the message in subjects with scope.

I wish this might help the community

Bro chill out, all I am saying is why do all the AI generated text need to be so long. Any human, you included, is able to write it in a few clear understandable lines of text, no AI needed to add many words without additional meaning.


No worries, In this particular context, Using AI tools to generate content might be because phrasing and repeating sentences in different ways will enlarge exposure of the content by the crawlers to give better SEO and to have more visibility to the content.


It may increase the SEO and visibility, but as a developer I stopped reading after the first few sentences. The idea is clearly written in the first paragraph, more is not needed. The rest is more interesting for documentation/archive purposes, to add reasoning and examples why this functionality is needed.

Basically you ask for the current workaround of using WebSockets for 'real-time updates', to be automatically included in the OutSystems platform to (hopefully) lower the bar of implementation complexity. And to be able to build applications that rely on the real-time updates to work properly with less steps to develop them.

It is perfectly justified to be lengthy text especially when you are trying to request a feature. By stating use cases and business value, those who need to evaluate the idea based on their own set of rules can appreciate it.