>> * Was your client on your desktop or up in the cloud in the same region as
>> the database?
All in azure same region.
>> * Are you using a different Guid as the partition key for each document?
>> You're supposed to be more "coarse" and group large groups of documents into
>> partitions
>
> Only just saw this. I have worked with a designed a solution using
> CosmosDb which is currently in production. I actually just released a blog
> post on client performance related to CosmosDb here:
> https://weblogs.asp.net/pglavich/cosmosdb-and-client-performance
>
I just read it all, well d
Sorry for the delay,
Only just saw this. I have worked with a designed a solution using CosmosDb
which is currently in production. I actually just released a blog post on
client performance related to CosmosDb here:
https://weblogs.asp.net/pglavich/cosmosdb-and-client-performance
As to y
I am half way through the Scott Wlaschin Video which makes a great case
for F# as a DDD tool.
I love the Card Game example.
module CardGame =
type Suit = Club | Diamond |Spade : Heart
type Rank = Two | Three | Four | Five | Six | Seven | Eight |
Nine | Ten | Jack | Queen
}
>
>
>
>
>
> However when I try to create a class diagram in VS2017 no association
> draws between the two interfaces.
>
>
>
> Is there a better way?
>
> Thank you
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
http://prdlxvm0001.codify.net/pipermail/ozdotnet/attachments/20180206/8a946347/attachment-0001.html
--
___
ozdotnet mailing list
ozdotnet@ozdotnet.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozdotnet
End of ozdotnet Digest, Vol 98, Issue 6
***
Firstly, a decent UML modelling tool will let you hide all the internal guff,
and concentrate on the public API. I’ve used Sparx Enterprise Architect for
many years, would recommend.
If you still find that your diagrams are cluttered with public, but
non-business-relevant properties, your domai
