![](https://hexbear.net/pictrs/image/227e2224-21aa-4a02-a8e2-f2a00ca69c22.png)
![](https://lemmy.ml/pictrs/image/1f910de9-62b5-43a9-8c93-94821c945577.png)
14·
10 months agoHigh Availability stans are angry about your question.
Basically… both options are ambiguous. Would be best if they used a more unique name. Like a burrow (many lemmings build burrows).
High Availability stans are angry about your question.
Basically… both options are ambiguous. Would be best if they used a more unique name. Like a burrow (many lemmings build burrows).
Amazon has high turnover because their strategy is to burn through new graduates (the cheapest dev labor) before they get sick of the poor working conditions. This is identical to their warehouse employment strategy.
Both sever and instance have multiple meanings when it comes to deploying Lemmy though.
An instance is running Lemmy publicly, but also just running the APU creates an instance of that API. To scale, you’d probably run multiple instances of the web API.
Same applies to server, but worse. You could also call the web API a web server. You could also call a VM a server. You could also call the physical machine a VM is on a server.
When it comes to naming stuff, it’s best to find something unambiguous if it’s a core defining thing you want to tell people about. Private corps do this to build a “brand”, which is still a valuable thing for open projects so that they can gain adoption.