- if address is not an independent entity and it is only accessible via its parent, then build a separate model for address may not be a good idea.
Address maybe quite independent in terms of actions you can do with it (CUD), for many use cases it is convenient to hold the records inside person record, as NOSQL allows to do this (you get relatedness and order automatically, you need no joins). CUD ops on server side a little bit more difficult to do this such records (than having records in separate table/collection) , but not so much. And on client side it would very reasonable to have it in separate model and be able to perform operations with this records in standard way.