I’m trying to wrap my head around the Autonomi developer experience. Can you assist?
What I’m trying to figure out is how we can run a web app (i.e. server-side code & logic) on Autonomi, a la ASP.NET on IIS, etc. I do understand the basic principle at work here, yes—secure and private file handling—but as we know there’s a lot more to a business application than just file storage & retrieval.
For some reason I’m not able to get my head past the notion that an Autonomi-based website can only be comprised of static files, with no backend logic allowed.
e.g. If this do that, otherwise get a value from the array
Actually, this segues into a related topic that’s been on my mind for some time now.
What about data? How do we build a multi-user application that warehouses its data in a single location?
We need that Single Source of Truth™ that a central relational database provides. How do we go about using something like Entity Framework? Optimistic concurrency? Autoincrementing primary keys? Cascading deletes?
It seems a thorny problem.
Are these types of apps going to be possible at all with Autonomi?
This is what dweb enables. Not ASP.NET and other stacks but both the examples you described.
dweb provides a local REST API that lets a web app load from Autonomi and work exactly like a dynamic app using any REST API. The restriction is that the business logic is all in the app and not as middleware on the server.
The Fileman example shows how to do this using Svelte with dweb, but as it involves a REST API, any web framework can be used (though none is required).
Oh well - maybe worth mentioning that there really is not that many use cases where you need server side logic if you design the process correctly
As explained over there users of the autonomi network can verify who they are, they can sign data and data can be encrypted to only be read by them… So the ‘issue’ of not having server side computing is mainly a app design task in most use cases…