NoSql Databases Complex object CRUD operations Api Design Strategy

Consider an hypothetical example of the music app.

with json as 'song':{ 'name': 'coldplay paradise', 'artists':[ { 'name': 'chris Martin' 'role':{ 'id': 123, 'name': 'Lead Singer' } 'img': 'some url' },{ 'name': 'Guy Berryman' 'role':{ 'id': 124, 'name': 'Singer' } 'img': 'some url' } ... ], 'awards': ['Grammy',...] } Suppose if i have hypothetically 100 artists for a song and when i update the artist role or delete an artist in a song i dont want to send 100 artists and also i can update an artist and delete an other artists in one request.What would be the best design strategy to handle these kind of scenarios and with even complex nested objects and what would be best design pattern that suits this scenario.