Forge and Spring applications


We have a question about Unifying Atlassian Connect and Forge: An Update .

Our cloud applications are using Java and Spring instead of NodeJS server. All the tutorials and information we have seen so far are with NodeJS. Will this be considered as a part of the migration to Forge? Or should we consider a migration to NodeJS first? Atlassian-connect-spring-boot is the library we rely on.

Thank you in advance,


Hi @fkasapov,

Forge is very different from Connect, at least in the sense that you won’t be able to just use your existing code written for Connect and run it on Forge. You have two way to go here:

Hope this helps!


Thank you for your reply @SvenSchatter .

Just to make sure. After State 4 happens, will there be self-hosted applications or all cloud plugins will have to be implemented on Forge?


I think the blog post is pretty clear about that:

Before reaching the final state, State 4, an app must not store any data outside of the Atlassian cloud (either through migration or by design). In addition, an app must migrate any remote-hosted compute in the Atlassian cloud.)

So yes, if you want your app to reach State 4, everything will have to be on Forge. However, in the blog post it also says this:

Although strongly recommended, State 3 and State 4 are not hard requirements, leaving room for exceptional cases where apps cannot move away from “off-Atlassian” compute and storage. Examples of exceptional cases include:

  • Apps that are by nature integrations between the Atlassian platform and external applications.
  • Apps with extremely heavy compute and storage requirements that exceed Forge quotas.
  • Apps that require massive amount of data for machine learning or reporting purposes.