Hi, hoping someone can provide some guidance and clarity with an enhancement to our customization package.

To generalize, 

We have a custom class Widget that we use to track the status of entities being processed in an outside system. The Widgets are stored in the DB have a Widget Maintenance screen, and we use the REST endpoint to work with Widgets as needed.

To enhance performance, we would like to start batching requests to update Widgets. At present it seems the options are,

a) Send a text string to an action or class and deserialize it into Widgets.

b) Create a second DataSource that defines the Widget collection as a Details group so that Widgets are submitted in an array.

c) Re-architect so that Widgets are always a details collection and never accessible as a top-level object.

My gut is telling me that 'a' would violate best practices and that 'b' would as well for allowing deadlocks/collisions if the existing path were to update records at the same time as the batch process.

So, would it really be necessary to re-architect the Widget collection as a Details set in all paths or is there a simpler way that we're missing?

Thanks!

Mike