mountainreason

Author*

Fur sure. But I don't get how that leads to an expectation that our biology is computing and utilizing derivatives in a computational graph.

Point 22 seems to imply that the other finds it notable that that isn't happening.

Yeah thanks, me too. So I'm wondering what point 22 is getting at. How could that even be possible?

What would that look like. Is there an implementation of the finite difference method in biology somehow?

I dont get this. Just because you don't have the GIL doesnt mean that your previously single threaded code is now multithreaded and stepping on itself.

I think the idea with localized access is that reads coming in after the initial commit can hit a nearby db instance, rather than the single global instance.

I agree with you about horizontal scalability in general though, the data isn't being partitioned. I guess read heavy loads can be scaled.

Even with a transaction, if the processing involves external side effects, e.g. sending and email, the rollback won't matter and you still get at least once.

I dont have an answer, I'm just curious about something. I thought that the point of an outbox was that it was local, and could therefore be updated atomically along with any local db changes. What would happen if the orchestrator was unable to update the remote shared cache outbox after a local exception/rolled back transaction?

Yeah. I know. Why would the data already be sorted?

Wouldn't you at least be looking at nlog(n) for the sort in the merge join?