I have a rather general question regarding the atlassian plans of improving storage api.
Currently storage api works as a pretty basic key-value storage.
That sadly really limits the use of the api in real life situation. Basically only to storing configuration of project.
Consider I would like to migrate one of our plugins to Forge platform, the project uses rather non-trivial ERD.
For example let’s have main entity QCItem that has 2 1:N relationships and 2 M:N relationships that store data for the project.
That’s borderline impossible to turn into key-value storage (regardless of limitations of such storage) and even if I made some clever mechanics with key names it’s still a question of performance.
It looks like nightmare to convert considering in spring boot you can build these M-V-C rather quickly these days.
So what are the plans in this area? Can we hope for complex Entity relationships modelled in forge apps?
Or the direction is more of an forge+atlassian connect blend in, where forge will server the UI and data storage is handled by current spring boot (for example) implementations with vendor hosted data?
To me one of the main draws to moving from atlassian connect to forge is to let atlassian handle hosted data of addons so they can guarantee data residency for example, I don’t see this possible with current storage api.