I am trying to find information on best practices for json data. I am working on a client server app that will contain family information. For purposed of this question, this is an oversimplification of the database. I have a family table, an address table, and a family members table. There are also a number of other tables that contain email addresses, phone numbers, etc. For each family, there can be multiple addresses (for the old folks that fly south for the winter), and multiple family members and each family member can have multiple phone numbers and email addresses. The family UID is in each table to enable linking. To retrieve all information for a family, should I build a complex JSON string that contains all of the data that needs to be parsed out manually or should it be individual calls, 1 for the family details, 1 for the addresses, 1 for the family members, 1 for each family members email addresses, and 1 for each family member's phone numbers? The single call seems very complicated but the alternative seems like a lot of overhead with connections, etc.