ManagedCode.Storage.AzureDataLake
2.1.15-alpha
Prefix Reserved
dotnet add package ManagedCode.Storage.AzureDataLake --version 2.1.15-alpha
NuGet\Install-Package ManagedCode.Storage.AzureDataLake -Version 2.1.15-alpha
<PackageReference Include="ManagedCode.Storage.AzureDataLake" Version="2.1.15-alpha" />
paket add ManagedCode.Storage.AzureDataLake --version 2.1.15-alpha
#r "nuget: ManagedCode.Storage.AzureDataLake, 2.1.15-alpha"
// Install ManagedCode.Storage.AzureDataLake as a Cake Addin #addin nuget:?package=ManagedCode.Storage.AzureDataLake&version=2.1.15-alpha&prerelease // Install ManagedCode.Storage.AzureDataLake as a Cake Tool #tool nuget:?package=ManagedCode.Storage.AzureDataLake&version=2.1.15-alpha&prerelease
ManagedCode.Storage
Version | Package | Description |
---|---|---|
ManagedCode.Storage.Core | Core | |
ManagedCode.Storage.FileSystem | FileSystem | |
ManagedCode.Storage.Azure | Azure | |
ManagedCode.Storage.Aws | AWS | |
ManagedCode.Storage.Gcp | GCP | |
ManagedCode.Storage.AspNetExtensions | AspNetExtensions |
Storage
General concept
One of the key benefits of using a universal wrapper for cloud blob storages is that it provides a consistent, easy-to-use interface for working with different types of blob storage. This can make it much easier for developers to switch between different storage providers, or to use multiple providers in the same project.
A universal wrapper can also simplify the development process by providing a single set of methods for working with blob storage, rather than requiring developers to learn and use the different APIs provided by each storage provider. This can save time and reduce the complexity of the code, making it easier to write, maintain, and debug.
In addition, a universal wrapper can provide additional functionality that is not available through the individual storage providers, such as support for common patterns like asynchronous programming and error handling. This can make it easier to write high-quality, reliable code that is robust and resilient to errors.
Overall, using a universal wrapper for cloud blob storages can provide many benefits, including improved flexibility, simplicity, and reliability in your application. A universal storage for working with multiple storage providers:
- Azure
- Google Cloud
- Amazon
- FileSystem
Motivation
Cloud storage is a popular and convenient way to store and access data in the cloud. However, different cloud storage providers often have their own unique APIs and interfaces for accessing and manipulating data. This can make it difficult to switch between different providers or to use multiple providers simultaneously.
Our library, provides a universal interface for accessing and manipulating data in different cloud blob storage providers. This makes it easy to switch between providers or to use multiple providers at the same time, without having to learn and use multiple APIs.
Features
- Provides a universal interface for accessing and manipulating data in different cloud blob storage providers.
- Makes it easy to switch between providers or to use multiple providers simultaneously.
- Supports common operations such as uploading, downloading, and deleting data.
Connection modes
You can connect storage interface in two modes provider-specific and default. In case of default you are restricted with one storage type
Azure
Default mode connection:
// Startup.cs
services.AddAzureStorageAsDefault(new AzureStorageOptions
{
Container = "{YOUR_CONTAINER_NAME}",
ConnectionString = "{YOUR_CONNECTION_NAME}",
});
Using in default mode:
// MyService.cs
public class MyService
{
private readonly IStorage _storage;
public MyService(IStorage storage)
{
_storage = storage;
}
}
Provider-specific mode connection:
// Startup.cs
services.AddAzureStorage(new AzureStorageOptions
{
Container = "{YOUR_CONTAINER_NAME}",
ConnectionString = "{YOUR_CONNECTION_NAME}",
});
Using in provider-specific mode
// MyService.cs
public class MyService
{
private readonly IAzureStorage _azureStorage;
public MyService(IAzureStorage azureStorage)
{
_azureStorage = azureStorage;
}
}
<details> <summary>Google Cloud (Click here to expand)</summary>
Google Cloud
Default mode connection:
// Startup.cs
services.AddGCPStorageAsDefault(opt =>
{
opt.GoogleCredential = GoogleCredential.FromFile("{PATH_TO_YOUR_CREDENTIALS_FILE}.json");
opt.BucketOptions = new BucketOptions()
{
ProjectId = "{YOUR_API_PROJECT_ID}",
Bucket = "{YOUR_BUCKET_NAME}",
};
});
Using in default mode:
// MyService.cs
public class MyService
{
private readonly IStorage _storage;
public MyService(IStorage storage)
{
_storage = storage;
}
}
Provider-specific mode connection:
// Startup.cs
services.AddGCPStorage(new GCPStorageOptions
{
BucketOptions = new BucketOptions()
{
ProjectId = "{YOUR_API_PROJECT_ID}",
Bucket = "{YOUR_BUCKET_NAME}",
}
});
Using in provider-specific mode
// MyService.cs
public class MyService
{
private readonly IGCPStorage _gcpStorage;
public MyService(IGCPStorage gcpStorage)
{
_gcpStorage = gcpStorage;
}
}
</details>
<details> <summary>Amazon (Click here to expand)</summary>
Amazon
Default mode connection:
// Startup.cs
//aws libarary overwrites property values. you should only create configurations this way.
var awsConfig = new AmazonS3Config();
awsConfig.RegionEndpoint = RegionEndpoint.EUWest1;
awsConfig.ForcePathStyle = true;
awsConfig.UseHttp = true;
awsConfig.ServiceURL = "http://localhost:4566"; //this is the default port for the aws s3 emulator, must be last in the list
services.AddAWSStorageAsDefault(opt =>
{
opt.PublicKey = "{YOUR_PUBLIC_KEY}";
opt.SecretKey = "{YOUR_SECRET_KEY}";
opt.Bucket = "{YOUR_BUCKET_NAME}";
opt.OriginalOptions = awsConfig;
});
Using in default mode:
// MyService.cs
public class MyService
{
private readonly IStorage _storage;
public MyService(IStorage storage)
{
_storage = storage;
}
}
Provider-specific mode connection:
// Startup.cs
services.AddAWSStorage(new AWSStorageOptions
{
PublicKey = "{YOUR_PUBLIC_KEY}",
SecretKey = "{YOUR_SECRET_KEY}",
Bucket = "{YOUR_BUCKET_NAME}",
OriginalOptions = awsConfig
});
Using in provider-specific mode
// MyService.cs
public class MyService
{
private readonly IAWSStorage _gcpStorage;
public MyService(IAWSStorage gcpStorage)
{
_gcpStorage = gcpStorage;
}
}
</details>
<details> <summary>FileSystem (Click here to expand)</summary>
FileSystem
Default mode connection:
// Startup.cs
services.AddFileSystemStorageAsDefault(opt =>
{
opt.BaseFolder = Path.Combine(Environment.CurrentDirectory, "{YOUR_BUCKET_NAME}");
});
Using in default mode:
// MyService.cs
public class MyService
{
private readonly IStorage _storage;
public MyService(IStorage storage)
{
_storage = storage;
}
}
Provider-specific mode connection:
// Startup.cs
services.AddFileSystemStorage(new FileSystemStorageOptions
{
BaseFolder = Path.Combine(Environment.CurrentDirectory, "{YOUR_BUCKET_NAME}"),
});
Using in provider-specific mode
// MyService.cs
public class MyService
{
private readonly IFileSystemStorage _fileSystemStorage;
public MyService(IFileSystemStorage fileSystemStorage)
{
_fileSystemStorage = fileSystemStorage;
}
}
</details>
How to use
We assume that below code snippets are placed in your service class with injected IStorage:
public class MyService
{
private readonly IStorage _storage;
public MyService(IStorage storage)
{
_storage = storage;
}
}
Upload
await _storage.UploadAsync(new Stream());
await _storage.UploadAsync("some string content");
await _storage.UploadAsync(new FileInfo("D:\\my_report.txt"));
Delete
await _storage.DeleteAsync("my_report.txt");
Download
var localFile = await _storage.DownloadAsync("my_report.txt");
Get metadata
await _storage.GetBlobMetadataAsync("my_report.txt");
Native client
If you need more flexibility, you can use native client for any IStorage<T>
_storage.StorageClient
Conclusion
In summary, Storage library provides a universal interface for accessing and manipulating data in different cloud blob storage providers. It makes it easy to switch between providers or to use multiple providers simultaneously, without having to learn and use multiple APIs. We hope you find it useful in your own projects!
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- Azure.Storage.Blobs (>= 12.16.0)
- Azure.Storage.Files.DataLake (>= 12.14.0)
- Humanizer.Core (>= 2.14.1)
- ManagedCode.Communication (>= 2.0.23)
- ManagedCode.Storage.Core (>= 2.1.15-alpha)
- Microsoft.Extensions.Logging.Abstractions (>= 7.0.0)
- System.Linq.Async (>= 6.0.1)
-
net7.0
- Azure.Storage.Blobs (>= 12.16.0)
- Azure.Storage.Files.DataLake (>= 12.14.0)
- Humanizer.Core (>= 2.14.1)
- ManagedCode.Communication (>= 2.0.23)
- ManagedCode.Storage.Core (>= 2.1.15-alpha)
- Microsoft.Extensions.Logging.Abstractions (>= 7.0.0)
- System.Linq.Async (>= 6.0.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
2.1.15-alpha | 138 | 5/22/2023 |
2.1.14 | 255 | 5/21/2023 |
2.1.13 | 1,884 | 12/20/2022 |
2.1.11 | 518 | 10/18/2022 |
2.1.10 | 470 | 10/18/2022 |
2.1.9 | 458 | 10/18/2022 |
2.1.8 | 476 | 10/18/2022 |
2.1.7 | 477 | 10/18/2022 |
2.1.6 | 505 | 10/18/2022 |
2.1.5 | 473 | 10/17/2022 |
2.1.4 | 471 | 10/17/2022 |
2.1.3 | 489 | 10/17/2022 |
2.1.2 | 471 | 10/16/2022 |
2.1.1 | 489 | 10/16/2022 |
2.1.0 | 477 | 10/14/2022 |
2.0.18 | 397 | 10/14/2022 |
2.0.11 | 458 | 8/12/2022 |
2.0.10 | 386 | 8/12/2022 |
2.0.9 | 387 | 8/11/2022 |
2.0.8 | 416 | 8/10/2022 |
2.0.7 | 394 | 8/9/2022 |
2.0.6 | 404 | 8/9/2022 |
2.0.5 | 404 | 8/8/2022 |
2.0.4 | 427 | 7/27/2022 |
2.0.3 | 407 | 7/26/2022 |
2.0.2 | 392 | 7/25/2022 |
2.0.1 | 438 | 7/22/2022 |
2.0.0 | 387 | 7/22/2022 |
1.2.1 | 434 | 7/17/2022 |