This video continues the discussion of concurrency with a focus on pessimistic concurrency and object locking. As part of designing a domain model for an application you need to decide which object(s) will be locked when you edit various objects. GemStone enforces locks at the object level, but if an Employee object references an Address object, then locking the Employee will not prevent changes to the Address.