This package wraps the NuGet: Microsoft.Azure.Cosmos package,
exposing a simple dependency-injection enabled IRepository<T>
interface.
The repository is responsible for all
of the create, read, update, and delete (CRUD) operations on objects where T : Item
. The Item
type adds
several properties, one which is a globally unique identifier defined as:
[JsonProperty("id")]
public string Id { get; set; } = Guid.NewGuid().ToString();
Additionally, a type property exists which indicates the subclass name (this is used for filtering implicitly on your behalf):
[JsonProperty("type")]
public string Type { get; set; }
Finally, a partition key property is used internally to manage partitioning on your behalf. This can optionally be overridden on an item per item basis.
📣 Azure Cosmos DB - Official Blog
-
Create an Azure Cosmos DB SQL resource.
-
Obtain the resource connection string from the Keys blade, be sure to get a connection string and not the key - these are different. The connection string is a compound key and endpoint URL.
-
Call
AddCosmosRepository
:public void ConfigureServices(IServiceCollection services) { services.AddCosmosRepository(); }
The optional
setupAction
allows consumers to manually configure theRepositoryOptions
object:public void ConfigureServices(IServiceCollection services) { services.AddCosmosRepository( options => { options.CosmosConnectionString = "< connection string >"; options.ContainerId = "data-store"; options.DatabaseId = "samples"; }); }
-
Define your object graph, objects must inherit
Item
, for example:using Microsoft.Azure.CosmosRepository; public class Person : Item { public string FirstName { get; set; } public string LastName { get; set; } }
-
Ask for an instance of
IRepository<TItem>
, in this case theTItem
isPerson
:using Microsoft.Azure.CosmosRepository; public class Consumer { readonly IRepository<Person> _repository; public Consumer(IRepository<Person> repository) => _repository = repository; // Use the repo... }
-
Perform any of the operations on the
_repository
instance, createPerson
records, update them, read them, or delete. -
Enjoy!
When OptimizeBandwidth
is true
(its default value), the repository SDK reduces networking and
CPU load by not sending the resource back over the network and serializing it to the client. This is specific to writes,
such as create, update, and delete. For more information, see Optimizing bandwidth in the Azure Cosmos DB .NET SDK.
There is much debate with how to structure your database and corresponding containers. Many developers with relational
database design experience might prefer to have a single container per item type, while others understand that Azure Cosmos DB
will handle things correctly regardless. By default, the ContainerPerItemType
option is false
and
all items are persisted into the same container. However, when it is true
, each distinct subclass of
Item
gets its own container named by the class itself.
Depending on the .NET configuration provider your app is using, there are several well-known keys that map to the repository options that configure your usage of the repository SDK. When using environment variables, such as those in Azure App Service configuration or Azure Key Vault secrets, the following keys map to the RepositoryOptions
instance:
Key | Data type | Default value |
---|---|---|
RepositoryOptions__CosmosConnectionString | string | null |
RepositoryOptions__DatabaseId | string | "database" |
RepositoryOptions__ContainerId | string | "container" |
RepositoryOptions__OptimizeBandwidth | boolean | true |
RepositoryOptions__ContainerPerItemType | boolean | false |
RepositoryOptions__AllowBulkExecution | boolean | false |
{
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft": "Warning",
"Microsoft.Hosting.Lifetime": "Information"
}
},
"AllowedHosts": "*",
"RepositoryOptions": {
"CosmosConnectionString": "<Your-CosmosDB-ConnectionString>",
"DatabaseId": "<Your-CosmosDB-DatabaseName>",
"ContainerId": "<Your-CosmosDB-ContainerName>",
"OptimizeBandwidth": true,
"ContainerPerItemType": true,
"AllowBulkExecution": true
}
}
For more information, see JSON configuration provider.
{
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft": "Warning",
"Microsoft.Hosting.Lifetime": "Information"
}
},
"AllowedHosts": "*",
"Values": {
"RepositoryOptions:CosmosConnectionString": "<Your-CosmosDB-ConnectionString>",
"RepositoryOptions:DatabaseId": "<Your-CosmosDB-DatabaseName>",
"RepositoryOptions:ContainerId": "<Your-CosmosDB-ContainerName>",
"RepositoryOptions:OptimizeBandwidth": true,
"RepositoryOptions:ContainerPerItemType": true,
"RepositoryOptions:AllowBulkExecution": true
}
}
For more information, see Customizing configuration sources.
As a consumer of Azure Cosmos DB, you can choose how to partition your data. By default, this repository SDK will partition items using their Item.Id
value as the /id
partition in the storage container. However, you can override this default behavior by:
- Declaratively specifying the partition key path with
PartitionKeyPathAttribute
- Override the
Item.GetPartitionKeyValue()
method - Ensure the the property value of the composite or synthetic key is serialized to match the partition key path
- Set
RepositoryOptions__ContainerPerItemType
totrue
, to ensure that your item with explicit partitioning is correctly maintained
As an example, considering the following:
using Microsoft.Azure.CosmosRepository;
using Microsoft.Azure.CosmosRepository.Attributes;
using Newtonsoft.Json;
using System;
namespace Example
{
[PartitionKeyPath("/synthetic")]
public class Person : Item
{
public string FirstName { get; set; } = null!;
public string? MiddleName { get; set; }
public string LastName { get; set; } = null!;
[JsonProperty("synthetic")]
public string SyntheticPartitionKey =>
$"{FirstName}-{LastName}"; // Also known as a "composite key".
protected override string GetPartitionKeyValue() => SyntheticPartitionKey;
}
}
Visit the Microsoft.Azure.CosmosRepository.Samples
directory for samples on how to use the library with:
Thanks goes to these wonderful people (emoji key):
David Pine 💻 |
Invvard |
Richard Mercer 💻 |
Daniel Marbach 💻 |
Manuel Sidler 💻 |
Dave Brock 📖 💻 |
Cagdas Erman Afacan 💻 💡 |
dcuccia 💻 |
This project follows the all-contributors specification. Contributions of any kind welcome!