zlacker

Indeed, again you are right. I've gone through the same motions as you trying to understand why the webdev people make this so complicated.

For your specific question here: NUMA & cpu cores don't suffer from the P in CAP: network partitions. If one of your CPU cores randomly stops responding, your system crashes, and that's fine because it never happens. If one of your web servers stops responding, which may happen for very common reasons and so is something you should absolutely design for, your system should keep working because otherwise you cannot build a reliable system out of many disconnected components (and I do mean many).

Also note that there is no way to really check if systems are available, only that you cannot reach them, which is significantly different.

Then we've not even reached the point that the CPU die makes communication extremely fast, whereas in a datacenter you're talking milliseconds, and if you are syncing with a different system accross data centers or even with clients, that story becomes wildely different.

>>vouwfi+(OP)
> If one of your CPU cores randomly stops responding, your system crashes

Are you sure about that? I actually have no idea but I'm surprised by your claim.

>>ekjhgk+U4
I don't think I'm qualified to answer the question, and I also think it depends on terminology where maybe 'core' is the wrong thing to say, but regardless: my general point is that the assumptions that hold for CPUs don't hold for webservices, and that's where the design ethos between them splits.