Previously, updating a Forge app’s UI required invoking a Forge function again to get any updates. Not only is this limited functionality, but this also led to workarounds, like having to invoke polling, so as to get updates.
With the introduction of Realtime, Forge apps can now push data from a single app invocation to multiple clients without the need for all clients to re-invoke the app. This eliminates the need for manual refreshes and constant polling, thereby improving efficiency and user experience.
Forge Realtime will provide a more dynamic and responsive platform for app development, and we can’t wait to see the innovative solutions you will create with these new capabilities. Currently this feature is only available in Jira but we are working on introducing this feature to Confluence. For more details on how to use this feature, see here.
To start using this EAP, sign up using this EAP form.
can you share what kind of platform limits will be enforced for this feature? E.g. how many channels, how many concurrent subscribers for each channel, max payload sizes…
Also, do you plan on having an associated cost for using this feature? If so, what kind of pricing can we expect?
Hey Paolo!
Currently our platform can support the following:
60 published messages per second on the same channel
limit message sizes to 300kb
The limits are yet to be determined depending on the outcomes from this EAP.
For associated cost, we’re currently still exploring what this might look like, taking in feedback from this EAP and market insights. Currently there’s no plan to apply costs but this thread will be updated with any changes.
Did we understand correctly that the Global channels can be used across multiple different apps, so that our various apps can communicate with each other?
Hey Oliver!
Currently global channels are only global within a particular app installation. So apps aren’t able to communicate with each other. Was there a use case you were hoping to use cross app realtime communication for?
Hi @RhysDiab,
This feature is currently in EAP and required a signup form for it to be used in your app (linked in the above message). EAP features cannot be rolled out to production yet but we’re looking to elevate this to Preview on October 31st.
We’re excited to share that the Forge Realtime platform feature is moving from Early Access Program (EAP) to Preview now! See changelog.
Thank you to everyone who participated in EAP and provided valuable feedback, your input has been instrumental in shaping the feature. As we enter into Preview, Realtime will be available in Confluence and Jira. See documentation for more information and more details on what’s changed from EAP.
The pricing model for Forge Realtime is not yet confirmed. We’ll share full details ahead of General Availability (GA). As with other Forge features, our plan is to offer a free tier, with pricing by consumption above this tier. Our approach will be in line with industry standards and based on real-world usage and costs. There will be no changes to your current access or quotas during Preview.
Please continue to share your feedback and use cases as you build with Forge Realtime and stay tuned for updates as we approach general availability and finalise the pricing model.
Thanks for being part of the Forge community and helping us shape the future of real-time capabilities on Atlassian!