@TrailMarks recently tweeted about some of their favourite dweb protocols, including Fission.
The slide behind @jamie247 of the Unbundling the Cloud Platform has a great list which is pretty much how we think about it at Fission, so I’m reproducing the table here:
|Authority||Controlled by the platform||Controlled by the user|
|Access||Users ask the platform for permission to use their data||Applications ask for user’s permission to use their data|
|Data||Bundled with the platform||Reusable and shared between applications|
|Architecture||Millions of users in one big database owned by the platform||Countless small databases owned by the user|
|Terms||Platforms dictate the rules||Users are free to switch to better terms or user experience|
For databases and apps, they are today most often hosted on behalf of many users, and so need to be designed “multi-tenant”. This means creating access control lists and separating user data from each other.
Fission apps are “single tenant” – user data is stored with the users, after the user gives permission to the app to access that data and storage.