ODC Events - client side subscription
416
Views
2
Comments
New
Frontend (App Interfaces)

Events in ODC is a great step towards an event driven architecture. 

In the current implementation, it only allows for server side consumers and I'd like to see that expanded to client side consumers as well.

Imagine I'm building a real time application with OutSystems and I want my UI to be refreshed as soon as some backend process is done. Currently, I need to manually integrate with some web socket / server sent event service to achieve this functionality. From my experience this is a convoluted process that requires a lot of time and the purchase of third party services. This is not the low code way.

Since now OutSystems has the Event primitive, it's the perfect time to add this capability.

Really nice idea! The ODC events represent a significant advancement towards adopting an event-driven architecture, and adding support for client-side consumers would be a significant improvement.

At the moment, real-time updates to the UI require some form of integration with WebSockets or Server-Sent Events, which adds complexity and often calls for external solutions. This infringes on the low-code philosophy of OutSystems.

It seems that if client-side event consumption is enabled, it would make developing real-time applications a lot easier. Perhaps one way to tackle this problem is to allow reactive subscriptions directly as client-side logic, which would greatly reduce the scope of custom coding needed.

Can't wait to know what the OutSystems team thinks about this one! 

This is not an original idea, OutSystems already shared that they will also implement Client side events, during the introduction of the Server Side events. It is however not yet prioritized in the ODC roadmap for 2025. Which I think is very unfortunate.