You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if Deno Deploy decided on a branded name for the product(s) it offers. Naming a thing is fundamental. It allows to communicate information about that thing. Without a name you can not talk about that thing. And if you want to offer multiple products in the future there need to be names to distinguish between them.
Currently, Deno Deploy's single product is a FaaS running in multiple distributed instances accessible through the public Internet. The name should reflect that there are multiple and that they are public. The multiple instances talk to many users like employees in multiple stores talk to many customers. Examples for the name could be "Actor", "Distributor", "Employee", etc. For comparison, CF calls this a “Worker”, although "working" is arguably not a useful distinction since any service performs work.
In the future you may want to add another product: a FaaS running in a single instance accessible only by other instances #88. The name should reflect that there is only one and that it's not public. The one instance talks to many other instances like one manager talks to many employees. Examples for the name could be "Coordinator", "Manufacturer", "Manager", etc. For comparison, CF calls this a “Durable Object” which… let‘s not talk about this further.
The text was updated successfully, but these errors were encountered:
It would be helpful if Deno Deploy decided on a branded name for the product(s) it offers. Naming a thing is fundamental. It allows to communicate information about that thing. Without a name you can not talk about that thing. And if you want to offer multiple products in the future there need to be names to distinguish between them.
Currently, Deno Deploy's single product is a FaaS running in multiple distributed instances accessible through the public Internet. The name should reflect that there are multiple and that they are public. The multiple instances talk to many users like employees in multiple stores talk to many customers. Examples for the name could be "Actor", "Distributor", "Employee", etc. For comparison, CF calls this a “Worker”, although "working" is arguably not a useful distinction since any service performs work.
In the future you may want to add another product: a FaaS running in a single instance accessible only by other instances #88. The name should reflect that there is only one and that it's not public. The one instance talks to many other instances like one manager talks to many employees. Examples for the name could be "Coordinator", "Manufacturer", "Manager", etc. For comparison, CF calls this a “Durable Object” which… let‘s not talk about this further.
The text was updated successfully, but these errors were encountered: