Page Comparison

...

1. Data from a bulk insert is converted/processed on the server.
   1. The client should only send data over the wire once, at which point the server is responsible for the rest of the work.
2. We "add" instead of "set" data from a bulk insert.
   1. The term "insert" does not imply the deletion of any data, so "adding" is more intuitive.
   2. Unlike the "set" method, "add" is defined at the Engine level, which means it can be used in an atomic operation.
3.  A bulk insert is a non-retry atomic operation that can fail (similar to verifyAndSwap)
   1. This means that a bulk insert cannot contain any data that already exists in the record.
4. A JSON string is used to define the data for a bulk insert.
   1. JSON is simple and has support in many languages
   2. We imagine that most data to be bulk inserted will come from web forms via AJAX in the form of JSON, so the application backend can pass it off to the database directly without the need to do additional conversion.
5. JSON value conversion semantics:

   1. Number → the appropriate integer, long, float or double

      1. May make sense to leverage convert code being written for the Import Framework

   2. String → string

   3. Boolean → boolean

   4. Object → a record is created and the key is linked to that record

   5. Array → Each element of the array is added as a value to the key

   6. Null → not permitted
6. There are features we are intentionally not supporting at the moment:
   1. Bulk Delete
   2. A compound operation to do a bulk insert for many records in one call (i.e. a mapping from record to json string as a param, or specifying multiple records in the json string)

...