The one relocation.

Object orientation drew the encapsulation boundary around the object: its data and the methods over that data lived together, and the boundary was the object’s own surface. The Branded Component System keeps encapsulation and moves the boundary outward, around the system. The state an object used to hold privately now lives inside the system that owns it, and what leaves the object is the one thing a distributed program can carry between machines — its name.

The relocation promotes the name from a detail to the interface. A system no longer hands another system a reference to an object; it hands a branded identity and a message about it, and everything the receiver can do, it does by asking the owner. The coupling that once travelled as a shared object now travels as a question about a name.

The move looks like a loss — you give up the convenience of reaching into an object — and it buys three things the object model could not keep across a boundary: a value that survives the process, a value that means the same thing on another machine, and a value a database can hold and order. The rest of the course is the consequence of this one line, drawn around the system instead of the object.