Use the actor model to design your code. Include a supervisor tree in your design so that the supervisors will notice when a piece has segfaulted (or is leaking

Use the actor model to design your code. Include a supervisor tree in your design so that the supervisors will notice when a piece has segfaulted (or is leaking memory) and deal with it, This is not rocket science and really has nothing to do with ObjectiveC. Any kind of serverside app could segfault or use up all available RAM. People have solved this problem in other languages and it is easy enough to solve the problem in ObjectiveC as well. There are bindings for ZeroMQ http://zeromq.org/bindings:objc http://zeromq.org/bindings:objc which is all you really need to deal with stability issues.