A quick Friday query ... Is anyone here using Cosmos DB in anger? I only ask because I just returned to experiment with it for the first time since it changed name to Cosmos. I actually quite like it! The .NET SDK wraps reasonably sensible classes over the API and I had a demo program up and running quickly.
I notice there are no "batch" operations for bulk inserts like we have in Table Storage, and I'm not writing JavaScript procs. It was unclear how to mix different document types in the same collection and process them separately (using a bool flag property in each type is to the way to go). There is little guidance about how to use the unique string Id. I haven't figured out how to add attachment links yet. But despite some oddities about the way it works, I'm really impressed with the performance, the magical indexing and ease-of-use. I'm thinking of moving my "music database" out of SQL Server into Cosmos and writing a fresh UI. This is my hobby project that has been going since 1992 and has never been completed because a new technology or fad comes along annually and forces an Xmas holiday rewrite. I realise now that cataloguing items like music, videos and books has always produced rather strict and complicated normalised SQL database tables. These sorts of items feel much more natural when converted to de-normalised documents. *Greg K*
