I'll probably write an article on my biggest issue with Vikram's approach, as it still encourages one to write boilerplate code, just in a different manner.

Regardless, that was basically my point with the UserService example and its protected user variable. The only way to affect a change visible to the rest of the program is to ask the service to handle it.

All change logic is encapsulated.