Description
A set of components to take the most advantage of performance and capacity of Azure Storage.
Hydra is Azure Subscription agnostic, which means it is possible to use Storage Accounts from different Azure Subscriptions. This functionality gives the developer configurable IOPS and Disk Space with no upper limits.
Mailcloud.Hydra alternatives and similar packages
Based on the "Database" category.
Alternatively, view Mailcloud.Hydra alternatives based on common mentions on social networks and blogs.
-
-
-
Event Store
EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures -
-
SqlKata Query Builder
SQL query builder, written in c#, helps you build complex queries easily, supports SqlServer, MySql, PostgreSql, Oracle, Sqlite and Firebird -
-
-
-
NReco LambdaParser
Runtime parser for string expressions (formulas, method calls). Builds dynamic LINQ expression tree and compiles it to lambda delegate. -
ZoneTree
ZoneTree is a persistent, high-performance, transactional, ACID-compliant ordered key-value database for NET. It can operate in memory or on local/cloud storage. -
-
StringDB
StringDB is a modular, key/value pair archival DB designed to consume *tiny* amounts of ram & produce *tiny* databases. -
Db4o-gpl
new Db4o GPL Source Code for Java7+ & .netstardard2.0 Android Xamarin..., the best database project to help you to learn how to make databases
WorkOS - The modern identity platform for B2B SaaS
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Mailcloud.Hydra or a related project?
README
Obsolete
Hydra
A set of components to take the most advantage of performance and capacity of Azure Storage.
Hydra is Azure Subscription agnostic, which means it is possible to use Storage Accounts from different Azure Subscriptions. This functionality gives the developer configurable IOPS and Disk Space with no upper limits.
Overview
Hydra.Core
class Hydra : IHydra
A central component for scaling across multiple Storage Accounts. It is using an ISharding strategy to compute consistent hashes that pick a right Storage Account by key provided.
class JumpSharding : ISharding
Default implementation of ISharding provided is JumpSharding that implement's Jump Consistent Hash.
Disclaimer
Hydra.Core doesn't manage shard migration, which means you are constrained the amount of Storage Accounts you start of with. The more the better.
Advanced usage
It is possible to have multiple instances of Hydra, configured to point at different and/or the same Storage Accounts, with different and/or the same ISharding implementations. That feature gives the developer maximum flexibility for making sure the right data is distributed in the right way.
Example
Example usage can be found in the Hydra.Tests.Integration namespace.
Hydra.Events
class StreamContainer : IStreamContainer
A central component for managing Stream's underlying storage. It requires an IHydra component to gain access to the storage.
class Stream : IStream
This component is in charge of writing and reading events to a stream in storage.
Disclaimer
Hydra.Events has a limitation dictated by Azure Storage. Currently one stream can consist of up to 50,000 events and 195GB of space.
Example
Example usage can be found in the Hydra.Tests.Integration namespace.