I read about SCORU and listented to last Teztalk with Yann about rollups but I am still unsure about one thing:
Lets say I have a rollup and I see an influx of users and need to scale up. I can simply create more rollups right? But the point I am missing here is - the new rollups I add to scale up, each has its own sr1 address right? So thas means that they are kind of its "own system". What I mean is are they all interoperable between each other? Or do the user need to do additional steps to bridge between rollups? Even if all rollups I deploy are meant for one single dApp still each rollup is different and has its own sr1 address? So for my understanding its not a "single" system.
If someone could elaborate and explain please as this still is not clear to me.. thanks
Followup Question to Arthur B response:
As far as I know deploying a rollup will cost 10k Tez as security deposit.
Lets say dApp XYZ runs on a rollup. XYZ gets popular and need to scale up horizontally -> need to deploy more rollups for XYZ
Users can move assets from one rollup to the other without needing a trusted bridge without additional user friction. The user does not even recognize that he is moving assets from one rollup to another - correct?
Now the limitations - slow inter roll-up synchronisation would be user friction -> can lead to bad UX due to waiting time?
When I interact with dApp XYZ that runs on several rollups, can it happen that I would wait for a longer time than the usual tx confirmations because of the roll-up synchronization?
And when it comes to the 10k security bond for running a rollup. If a dApp XYZ needs to deploy more rollups, does it need to put the 10k bond for every rollup? If this is the case isnt that a hefty "cost" and big barrier to achieve scalability on a high level?