How do you think about cross-tenancy calls? IIRC, this model assumes everyone is in the same codebase and compute fabric. Something like Share brings the code to the caller, which is great for efficiency, but not great for IP protection. Do you essentially just use the Unison proxy for cross-tenancy situations (and just use Unison on both sides)? That gives you essentially the same network and code/data privacy isolation we have today. Or do you see a world where things go the other direction: Tenancy A's application code moves toward Tenancy B's data (essentially in B's enclave), where it can do arbitrary computation on it, and then some data policy (also defined in Unison) allows some data to make it back to Tenancy A?
I understand when you say that some callers bring code to execute locally (thereby improving latency), but that only makes sense for stateless code-which can be solved by using libraries. What about stateful or persistence-related code, which (I guess) tends to account for most of the headaches?
How do you think about cross-tenancy calls?
IIRC, this model assumes everyone is in the same codebase and compute fabric. Something like Share brings the code to the caller, which is great for efficiency, but not great for IP protection.
Do you essentially just use the Unison proxy for cross-tenancy situations (and just use Unison on both sides)? That gives you essentially the same network and code/data privacy isolation we have today.
Or do you see a world where things go the other direction: Tenancy A's application code moves toward Tenancy B's data (essentially in B's enclave), where it can do arbitrary computation on it, and then some data policy (also defined in Unison) allows some data to make it back to Tenancy A?
I understand when you say that some callers bring code to execute locally (thereby improving latency), but that only makes sense for stateless code-which can be solved by using libraries. What about stateful or persistence-related code, which (I guess) tends to account for most of the headaches?
Yeah it’s a fascinating idea but I’m struggling to understand what happens when that album or thumbnail service naturally needs to talk to its db
@@jakeclearythis is just a BS tool that some nerd made. Stick with tried and true tools
@@spartanghost_17 this shit is amazing for startups, hackathons, and side projects.