What are the pain points of deploying Swift on Server applications?

[sspringer (Stefan Springer)]

@jaleel

Potentially one can write a distributed actors runtime using system processes, where memory is isolated, so killing it won't do any harm to other parts of an app.

I am trying something like this there, maybe others might join the efforts (or write something better). (UPDATE: I started a separate topic on this.) But this has overhead.

@taylorswift

there’s a really simple counterargument to this, which is cost.

Well, I think it is also about selling your application (in cases where it is not you who is actually running it). The customer might want to run only one instance (maybe as a first deployment), and telling the customer that a failure in a single request might crash the whole application is not a good selling point.

@sspringer

I wonder if the safety guarantees to prevent data conflicts in parallel code that came with Swift 6 could help isolate at least some (or all?) of these fatal errors in concurrent contexts.

Sorry for quoting myself, but maybe one of the compiler people could comment this, would be interesting to know. Thanks.

@sliemeobn

I personally think is a bit too prominently placed here on the pain points for swift on server list.

Yes, the discussion about this point got big here, could better be a topic on its own. But it seems to be a major pain point for some people (including me).

UPDATE: I started a separate topic on this.