ORM isn't the anti-pattern, but rather the current way we do OOP. Object orientation is a pervasive, powerful paradigm, but our current approach only works for

ORM isn't the anti-pattern, but rather the current way we do OOP. Object orientation is a pervasive, powerful paradigm, but our current approach only works for in-process, highly interlinked, synchronous objects. We need to move to OOP more similar to Erlang. Message based, where the messages are values, not references to references of references, which is the case with Java-style objects (you work with an object via a handle, which is in fact a reference to the object, allowing mutable shared state).