Migrating from Heroku Redis to Forge

Hi everyone,

My Connect app currently relies on Redis hosted on Heroku. I’m planning a full migration to Atlassian Forge, but I haven’t found a clear way to integrate Redis within the Forge environment.

Has anyone successfully used Redis with a Forge app, or does anyone have information on potential solutions or alternatives? Any insights or experiences would be greatly appreciated!

Thanks!

Hi @HungTran,

There’s no built-in cache capability within Forge that’s ready for production usage. We have a Cache API that’s currently available in early access.

We have a public roadmap item tracking the delivering of Forge cache to Preview, but there is no committed date for this yet.

Depending on your use case for the cache, you could:

  • Evaluate using the Forge key/value store instead
  • Continue to use an external redis provider and interact with it over a HTTPs/REST API.
  • Pause your adoption of hosted Forge features (and instead use the incremental adoption pathway) until Forge Cache is production ready.

Hi HeyJoe

Thanks for the information. For now, we will postpone the migration to using Forge modules for the entire application while still using Forge remote as it is now, waiting for more new parts to be supported by Forge

Best regards
Hung

1 Like