Aquiles Wiki Rss Feed

New Comment on "Installing Cassandra"

Ghoneim — Tue, 07 Feb 2012 04:12:19 GMT

Please add semicolon ; after the connection code as I got very confused because of this ! Regards,

Updated Wiki: Aquiles.Connection.Pooling.SizeControlledConnectionPool

javiercanillas — Thu, 19 Jan 2012 16:43:25 GMT

SizeControlledConnectionPool

Description

This implementation of Aquiles.Connection.Pooling.IConnectionPool has a pooling mechanism with the following features:

Warm-up capabilities
Minimum and maximum size control for connection within the pool

This implementation also support for configuring all this features by adding some entries in the SpecialConnectionParameters within the connection node inside the AquilesConfiguration:

minimumClientsToKeepInPool (default 10): let you set the number of connections to keep in the pool.
maximumClientsToSupportInPool (default 1000): let you set the number of connections to handle within the pool after which the pool will no longer create any new connection.
*poolDueTime" (default never): time to wait to start the cleaning thread on the pool.
poolPeriodicTime (default never): time to wait between each cleanse.
endpointManagerDueTime (default): time to wait to start the health checker on blackisted endpoints.
endpointManagerPeriodicTime (default): time to wait between each health checking.
maximumRetriesToPollClient (default 0): how many times an execution will be retried before a fail. A retryable error would be if the connection is closed or something similar.
magicNumber (default 7): let you set a divider number which will be use to choose how many iddle connections will be free on each run of the garbage collector of idle connections.

To clarify this use, consider the following ecuation:
Qm = minimum quantity of connections to keep
QM = maximum quantity of connections to keep / create
mM = magic number
FC = Connections to free from the idle list

then

FC = (QM - Qm) / mM

So, it will take the amount in FC from the iddle list. This process will control to leave, at least, the minimum quantity configured in the list.

Also, you can set the retry quantity when polling connection from the pool by using the property maximumRetriesToPollClient. Default value of this property is 0.

An example of configuration:

        <connection poolType="" factoryType="BUFFERED">
          <specialConnectionParameters>
            <add key="minimumClientsToKeepInPool" value="20" />
            <add key="maximumClientsToSupportInPool" value="1000" />
            <add key="magicNumber" value="7" />
            <add key="maximumRetriesToPollClient" value="3" />
          </specialConnectionParameters>
        </connection>

Summary

Type: Internal Class
Namespace / Package: Aquiles.Connection.Pooling
All implemented interfaces: Aquiles.Connection.Pooling.IConnectionPool
All extended interfaces: None
All extended classes: Dont apply
Direct Known interfaces: None
Direct Known classes: None

Constructors

No public constructor available

Properties from Aquiles.Connection.Pooling.IConnectionPool

public string Name

public Aquiles.Connection.Endpoint.IEndpointManager EndpointManager

public Aquiles.Connection.Factory.IConnectionFactory ConnectionFactory

public Aquiles.Configuration.SpecialConnectionParameterCollection SpecialConnectionParameters

Methods from Aquiles.Connection.Pooling.IConnectionPool

public void Initialize()

public Aquiles.Model.Internal.CassandraClient Borrow()

public void Release(Aquiles.Model.Internal.CassandraClient cassandraClient)

public void Invalidate(Aquiles.Model.Internal.CassandraClient cassandraClient)

Updated Wiki: Aquiles.Connection.Pooling.SizeControlledConnectionPool

javiercanillas — Thu, 19 Jan 2012 16:40:15 GMT

SizeControlledConnectionPool

Description

This implementation of Aquiles.Connection.Pooling.IConnectionPool has a pooling mechanism with the following features:

Warm-up capabilities
Minimum and maximum size control for connection within the pool

This implementation also support for configuring all this features by adding some entries in the SpecialConnectionParameters within the connection node inside the AquilesConfiguration:

minimumClientsToKeepInPool (default 10): let you set the number of connections to keep in the pool.
maximumClientsToSupportInPool (default 1000): let you set the number of connections to handle within the pool after which the pool will no longer create any new connection.
*poolDueTime" (default never): time to wait to start the cleaning thread on the pool.
poolPeriodicTime (default never): time to wait between each cleanse.
endpointManagerDueTime (default): time to wait to start the health checker on blackisted endpoints.
endpointManagerPeriodicTime (default): time to wait between each health checking.
magicNumber (default 7): let you set a divider number which will be use to choose how many iddle connections will be free on each run of the garbage collector of idle connections.

FC = (QM - Qm) / mM

        <connection poolType="" factoryType="BUFFERED">
          <specialConnectionParameters>
            <add key="minimumClientsToKeepInPool" value="20" />
            <add key="maximumClientsToSupportInPool" value="1000" />
            <add key="magicNumber" value="7" />
            <add key="maximumRetriesToPollClient" value="3" />
          </specialConnectionParameters>
        </connection>

Summary

Constructors

No public constructor available

Properties from Aquiles.Connection.Pooling.IConnectionPool

public string Name

public Aquiles.Connection.Endpoint.IEndpointManager EndpointManager

public Aquiles.Connection.Factory.IConnectionFactory ConnectionFactory

public Aquiles.Configuration.SpecialConnectionParameterCollection SpecialConnectionParameters

Methods from Aquiles.Connection.Pooling.IConnectionPool

public void Initialize()

public Aquiles.Model.Internal.CassandraClient Borrow()

public void Release(Aquiles.Model.Internal.CassandraClient cassandraClient)

public void Invalidate(Aquiles.Model.Internal.CassandraClient cassandraClient)

Updated Wiki: Aquiles.VersionHistory

javiercanillas — Mon, 16 Jan 2012 18:11:21 GMT

Version History

Planning changes
- using individual pools for each Keyspace connected from a cluster, doing so we avoid a roundtrip to set such keyspace on the connection before using it.

v1.0.0.1 & v0.7.0.9 & v0.8.0.2
Fixed When a node is down, and then restarted it will swap between blacklist and available list

v1.0.0.0
added support for Cassandra 1.0.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.8.0.1
added support for Cassandra 0.8.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.7.0.8
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v.0.7.0.6
- Added AquilesKeyRange the properties: StartToken and EndToken
- Changed the converter to support these new properties
- Added a GetKeyRangeSliceCommandTest method to test this new approach.
- 2 new encoders for Long (Big-Endian and Little-Endian). Please use these if you need to use the columns for second indexes. Use Big-Endian implementations for most of Cassandra versions, since Java default implementation of Long to ByteArray (and viceversa) is Big-Endian.
- moved Logging namespace to Diagnostics
- Added an Interface to support MonitoringFeatures (like time on borrows, releases, quantity of active connections, inactive connections and so on)
- Added a Helper to support the above feature internally
- Added a new property on the configuration section to be able to add your own implementation of IMonitorFeatures to log such information
- Added a whole new project that use PerformanceCounterHelper (see http://perfmoncounterhelper.codeplex.com) to submit the collected features values into Performance Counter.

v0.7.0.5
- fix GetKeyRangeSliceCommand doesn't support for empty Start and End Key
- Also fix that AquilesTokenRange structure to match Cassandra structure
- Modified RetrieveKeyspaceDistributionComand to return a list of AquilesTokenRange.
- added KeyspaceConnectionPool to avoid 1 roundtrip to Cassandra Cluster. Still on test!!!
- fix AquilesColumn has TTL as required, but it is optional in Cassandra
- fix UnavailableException and TimedOutException is not meaning of connection broken

0.7.0.4
- added a new ColumnFamily with TimeUUID comparator.
- SizeControlledConnectionPool: now throws an exception if the cluster has no valid endpoints when creating a new connection
- DefaultAquilesCluster: taking out the validation on the endpoints to assure they al point to the same cluster due to some problems when 1 endpoint is taken down after creating connection pool.
- Added support for "getindexedslices" that let you do a search with some conditions.

0.7.0.3
- Added Validation for TTL of Columns when inserting a column
- Added DateTimePrecise from http://www.codeproject.com/KB/cs/DateTimePrecise.aspx?display=Print to properly generate random Guid based on a more precise time data.
- Added a UUIDEncoderHelper that actually works with dotnet GUID but it converts to a byte[] structure compatible with Java UUID.
- Added Test for the above implementations and changes.
- fixed the UnixTimestamp. There was a bu* moved from Cassandra 0.7-beta2 to 0.7-beta2
- moved from thrift 0.2 to 0.5
- removed RenameColumnFamilyCommand and RenameKeyspaceCommand since they are not longer supported on Thrift API
- Optional properties on AquilesColumnFamily are now nullable to support default values within Cassandra Server.
- Added support for optional parameters on AquilesColumnFamilyConverterg that the actual DateTime was taken as UTC but the unitStartDateTime was not represented as UTC.
- Extended the TTL validation. It shouldn't let TTL value equal or below to zero.

0.7.0.2
- taken out all the keyspace and columnfamily validation since Cassandra 0.7.0-beta1 work with this on the fly
- Thrift structure converters created.
- changed command logic when creating and updating data to use converters.
- The GetKeyRangeSliceCommand threw a null reference exception when building output response. Fixed by Aaron8498.
- expose CfDef metadata in describe_keyspaces (CASSANDRA-1633)
- rename RackAwareStrategy to OldNetworkTopologyStrategy, RackUnawareStrategy to SimpleStrategy, DatacenterShardStrategy to NetworkTopologyStrategy, AbstractRackAwareSnitch to AbstractNetworkTopologySnitch (CASSANDRA-1392)
- remove keyspace argument from multiget_count (CASSANDRA-1422)
- Add AquilesColumnFamily.DefaultValidationClass (CASSANDRA-891)
- Add DescribeSplitsCommand to support describe_splits
- rename checkschemaagreement to describeschemaversions (CASSANDRA-1478)
- min, max compaction threshold are now configurable and persistent per-ColumnFamily (CASSANDRA-1468) (AquilesColumnFamily.MinimumCompactationThreshold and AquilesColumnFamily.MaximumCompactationThreshold)
- Removed Clock structure (CASSANDRA-1501)
- Added DescribeSnitchCommand to support new method describe_snitch in Thrift API (CASSANDRA-1490)
- v0.7.0.0-beta1
- Added preliminar support for Apache-Cassandra version 0.7-beta1

v0.6.4.2
- Moved SuperColumn Name and Columns names and values into Byte[]. Doing so, predicates and everything related to them are moved to Byte[] too. This will enable users to work with Long, TimeUUID and even Serializable Objects than can be converted into a Byte[].
- Added some useful EncoderHelpers in order to help clients to overcode this big change.
- Added more helpful methods and class comments.
- GetKeyRangeSliceCommand will now output a list of GetKeyRangeSliceCommand.Out class that now has the Key as property.

v0.6.4.1
- BatchMutateCommand with SuperColumns over a Standard ColumnFamily fixed
- MultiGetSliceCommand without SuperColumn over a Super ColumnFamily Type fixed

v0.6.4.0
- Added support for Apache Cassandra version 0.6.4.0
- Added support for the new method "describe_partitioner" through a new command called "RetrievePartitionerCommand"
- Added an static method called "RetrieveInformation" to "AquilesHelper" so you can get the configuration parameters of each cluster (local config and remote config)

v0.6.3.0
- Added support for Apache Cassandra version 0.6.3.0

v0.6.2.1
- Change version to match Apache Cassandra version
- Fixed DeleteCommand validation exception when column value is null

v1.0.0.1
- Fixed divide by zero in SizeControlledConnectionPool.controlIdleClientSizeMethod

v1.0.0.0
- Initial Release that support Apache Cassandra version 0.6.2
- Connection Pool: to avoid performance and resource problems under heavy traffic.
- Node Balancing for proper distribution of traffic: this will equally distribute the connections to a cluster between all the nodes configured to that cluster.
- Defensive node health check: when the framework detects a node is down, it will ban that node and every X seconds will attempt to connect to it. When this try success then that node is put back in the distrubution list.
- Command Validation: Before attempting to open a connection against a cluster, Aquiles will validate the Command Input (Column, SuperColumn, etc). It even will validate that the ColumnFamily exists within the KeySpace, and that the KeySpace exists within the cluster.

Updated Wiki: Aquiles.VersionHistory

javiercanillas — Mon, 16 Jan 2012 18:03:05 GMT

Version History

Planning changes
- using individual pools for each Keyspace connected from a cluster, doing so we avoid a roundtrip to set such keyspace on the connection before using it.

v1.0.0.1 & v0.7.0.9 & v0.8.0.2
Fixed When a node is down, and then restarted it will swap between blacklist and available list

v1.0.0.0
added support for Cassandra 1.0.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.8.0.1
added support for Cassandra 0.8.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.7.0.8
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v.0.7.0.6
- Added AquilesKeyRange the properties: StartToken and EndToken
- Changed the converter to support these new properties
- Added a GetKeyRangeSliceCommandTest method to test this new approach.
- 2 new encoders for Long (Big-Endian and Little-Endian). Please use these if you need to use the columns for second indexes. Use Big-Endian implementations for most of Cassandra versions, since Java default implementation of Long to ByteArray (and viceversa) is Big-Endian.
- moved Logging namespace to Diagnostics
- Added an Interface to support MonitoringFeatures (like time on borrows, releases, quantity of active connections, inactive connections and so on)
- Added a Helper to support the above feature internally
- Added a new property on the configuration section to be able to add your own implementation of IMonitorFeatures to log such information
- Added a whole new project that use PerformanceCounterHelper (see http://perfmoncounterhelper.codeplex.com) to submit the collected features values into Performance Counter.

v0.7.0.5
- fix GetKeyRangeSliceCommand doesn't support for empty Start and End Key
- Also fix that AquilesTokenRange structure to match Cassandra structure
- Modified RetrieveKeyspaceDistributionComand to return a list of AquilesTokenRange.
- added KeyspaceConnectionPool to avoid 1 roundtrip to Cassandra Cluster. Still on test!!!
- fix AquilesColumn has TTL as required, but it is optional in Cassandra
- fix UnavailableException and TimedOutException is not meaning of connection broken

0.7.0.4
- added a new ColumnFamily with TimeUUID comparator.
- SizeControlledConnectionPool: now throws an exception if the cluster has no valid endpoints when creating a new connection
- DefaultAquilesCluster: taking out the validation on the endpoints to assure they al point to the same cluster due to some problems when 1 endpoint is taken down after creating connection pool.
- Added support for "getindexedslices" that let you do a search with some conditions.

0.7.0.3
- Added Validation for TTL of Columns when inserting a column
- Added DateTimePrecise from http://www.codeproject.com/KB/cs/DateTimePrecise.aspx?display=Print to properly generate random Guid based on a more precise time data.
- Added a UUIDEncoderHelper that actually works with dotnet GUID but it converts to a byte[] structure compatible with Java UUID.
- Added Test for the above implementations and changes.
- fixed the UnixTimestamp. There was a bu* moved from Cassandra 0.7-beta2 to 0.7-beta2
- moved from thrift 0.2 to 0.5
- removed RenameColumnFamilyCommand and RenameKeyspaceCommand since they are not longer supported on Thrift API
- Optional properties on AquilesColumnFamily are now nullable to support default values within Cassandra Server.
- Added support for optional parameters on AquilesColumnFamilyConverterg that the actual DateTime was taken as UTC but the unitStartDateTime was not represented as UTC.
- Extended the TTL validation. It shouldn't let TTL value equal or below to zero.

0.7.0.2
- taken out all the keyspace and columnfamily validation since Cassandra 0.7.0-beta1 work with this on the fly
- Thrift structure converters created.
- changed command logic when creating and updating data to use converters.
- The GetKeyRangeSliceCommand threw a null reference exception when building output response. Fixed by Aaron8498.
- expose CfDef metadata in describe_keyspaces (CASSANDRA-1633)
- rename RackAwareStrategy to OldNetworkTopologyStrategy, RackUnawareStrategy to SimpleStrategy, DatacenterShardStrategy to NetworkTopologyStrategy, AbstractRackAwareSnitch to AbstractNetworkTopologySnitch (CASSANDRA-1392)
- remove keyspace argument from multiget_count (CASSANDRA-1422)
- Add AquilesColumnFamily.DefaultValidationClass (CASSANDRA-891)
- Add DescribeSplitsCommand to support describe_splits
- rename checkschemaagreement to describeschemaversions (CASSANDRA-1478)
- min, max compaction threshold are now configurable and persistent per-ColumnFamily (CASSANDRA-1468) (AquilesColumnFamily.MinimumCompactationThreshold and AquilesColumnFamily.MaximumCompactationThreshold)
- Removed Clock structure (CASSANDRA-1501)
- Added DescribeSnitchCommand to support new method describe_snitch in Thrift API (CASSANDRA-1490)
- v0.7.0.0-beta1
- Added preliminar support for Apache-Cassandra version 0.7-beta1

v0.6.4.2
- Moved SuperColumn Name and Columns names and values into Byte[]. Doing so, predicates and everything related to them are moved to Byte[] too. This will enable users to work with Long, TimeUUID and even Serializable Objects than can be converted into a Byte[].
- Added some useful EncoderHelpers in order to help clients to overcode this big change.
- Added more helpful methods and class comments.
- GetKeyRangeSliceCommand will now output a list of GetKeyRangeSliceCommand.Out class that now has the Key as property.

v0.6.4.1
- BatchMutateCommand with SuperColumns over a Standard ColumnFamily fixed
- MultiGetSliceCommand without SuperColumn over a Super ColumnFamily Type fixed

v0.6.4.0
- Added support for Apache Cassandra version 0.6.4.0
- Added support for the new method "describe_partitioner" through a new command called "RetrievePartitionerCommand"
- Added an static method called "RetrieveInformation" to "AquilesHelper" so you can get the configuration parameters of each cluster (local config and remote config)

v0.6.3.0
- Added support for Apache Cassandra version 0.6.3.0

v0.6.2.1
- Change version to match Apache Cassandra version
- Fixed DeleteCommand validation exception when column value is null

v1.0.0.1
- Fixed divide by zero in SizeControlledConnectionPool.controlIdleClientSizeMethod

v1.0.0.0
- Initial Release that support Apache Cassandra version 0.6.2
- Connection Pool: to avoid performance and resource problems under heavy traffic.
- Node Balancing for proper distribution of traffic: this will equally distribute the connections to a cluster between all the nodes configured to that cluster.
- Defensive node health check: when the framework detects a node is down, it will ban that node and every X seconds will attempt to connect to it. When this try success then that node is put back in the distrubution list.
- Command Validation: Before attempting to open a connection against a cluster, Aquiles will validate the Command Input (Column, SuperColumn, etc). It even will validate that the ColumnFamily exists within the KeySpace, and that the KeySpace exists within the cluster.

Updated Wiki: Aquiles.VersionHistory

javiercanillas — Mon, 16 Jan 2012 18:02:46 GMT

Version History

Planning changes
- using individual pools for each Keyspace connected from a cluster, doing so we avoid a roundtrip to set such keyspace on the connection before using it.

v1.0.0.1 & v0.7.0.9 & v0.8.0.2*
When a node is down, and then restarted it will swap between blacklist and available list

v1.0.0.0
added support for Cassandra 1.0.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.8.0.1
added support for Cassandra 0.8.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.7.0.8
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v.0.7.0.6
- Added AquilesKeyRange the properties: StartToken and EndToken
- Changed the converter to support these new properties
- Added a GetKeyRangeSliceCommandTest method to test this new approach.
- 2 new encoders for Long (Big-Endian and Little-Endian). Please use these if you need to use the columns for second indexes. Use Big-Endian implementations for most of Cassandra versions, since Java default implementation of Long to ByteArray (and viceversa) is Big-Endian.
- moved Logging namespace to Diagnostics
- Added an Interface to support MonitoringFeatures (like time on borrows, releases, quantity of active connections, inactive connections and so on)
- Added a Helper to support the above feature internally
- Added a new property on the configuration section to be able to add your own implementation of IMonitorFeatures to log such information
- Added a whole new project that use PerformanceCounterHelper (see http://perfmoncounterhelper.codeplex.com) to submit the collected features values into Performance Counter.

v0.7.0.5
- fix GetKeyRangeSliceCommand doesn't support for empty Start and End Key
- Also fix that AquilesTokenRange structure to match Cassandra structure
- Modified RetrieveKeyspaceDistributionComand to return a list of AquilesTokenRange.
- added KeyspaceConnectionPool to avoid 1 roundtrip to Cassandra Cluster. Still on test!!!
- fix AquilesColumn has TTL as required, but it is optional in Cassandra
- fix UnavailableException and TimedOutException is not meaning of connection broken

0.7.0.4
- added a new ColumnFamily with TimeUUID comparator.
- SizeControlledConnectionPool: now throws an exception if the cluster has no valid endpoints when creating a new connection
- DefaultAquilesCluster: taking out the validation on the endpoints to assure they al point to the same cluster due to some problems when 1 endpoint is taken down after creating connection pool.
- Added support for "getindexedslices" that let you do a search with some conditions.

0.7.0.3
- Added Validation for TTL of Columns when inserting a column
- Added DateTimePrecise from http://www.codeproject.com/KB/cs/DateTimePrecise.aspx?display=Print to properly generate random Guid based on a more precise time data.
- Added a UUIDEncoderHelper that actually works with dotnet GUID but it converts to a byte[] structure compatible with Java UUID.
- Added Test for the above implementations and changes.
- fixed the UnixTimestamp. There was a bu* moved from Cassandra 0.7-beta2 to 0.7-beta2
- moved from thrift 0.2 to 0.5
- removed RenameColumnFamilyCommand and RenameKeyspaceCommand since they are not longer supported on Thrift API
- Optional properties on AquilesColumnFamily are now nullable to support default values within Cassandra Server.
- Added support for optional parameters on AquilesColumnFamilyConverterg that the actual DateTime was taken as UTC but the unitStartDateTime was not represented as UTC.
- Extended the TTL validation. It shouldn't let TTL value equal or below to zero.

0.7.0.2
- taken out all the keyspace and columnfamily validation since Cassandra 0.7.0-beta1 work with this on the fly
- Thrift structure converters created.
- changed command logic when creating and updating data to use converters.
- The GetKeyRangeSliceCommand threw a null reference exception when building output response. Fixed by Aaron8498.
- expose CfDef metadata in describe_keyspaces (CASSANDRA-1633)
- rename RackAwareStrategy to OldNetworkTopologyStrategy, RackUnawareStrategy to SimpleStrategy, DatacenterShardStrategy to NetworkTopologyStrategy, AbstractRackAwareSnitch to AbstractNetworkTopologySnitch (CASSANDRA-1392)
- remove keyspace argument from multiget_count (CASSANDRA-1422)
- Add AquilesColumnFamily.DefaultValidationClass (CASSANDRA-891)
- Add DescribeSplitsCommand to support describe_splits
- rename checkschemaagreement to describeschemaversions (CASSANDRA-1478)
- min, max compaction threshold are now configurable and persistent per-ColumnFamily (CASSANDRA-1468) (AquilesColumnFamily.MinimumCompactationThreshold and AquilesColumnFamily.MaximumCompactationThreshold)
- Removed Clock structure (CASSANDRA-1501)
- Added DescribeSnitchCommand to support new method describe_snitch in Thrift API (CASSANDRA-1490)
- v0.7.0.0-beta1
- Added preliminar support for Apache-Cassandra version 0.7-beta1

v0.6.4.2
- Moved SuperColumn Name and Columns names and values into Byte[]. Doing so, predicates and everything related to them are moved to Byte[] too. This will enable users to work with Long, TimeUUID and even Serializable Objects than can be converted into a Byte[].
- Added some useful EncoderHelpers in order to help clients to overcode this big change.
- Added more helpful methods and class comments.
- GetKeyRangeSliceCommand will now output a list of GetKeyRangeSliceCommand.Out class that now has the Key as property.

v0.6.4.1
- BatchMutateCommand with SuperColumns over a Standard ColumnFamily fixed
- MultiGetSliceCommand without SuperColumn over a Super ColumnFamily Type fixed

v0.6.4.0
- Added support for Apache Cassandra version 0.6.4.0
- Added support for the new method "describe_partitioner" through a new command called "RetrievePartitionerCommand"
- Added an static method called "RetrieveInformation" to "AquilesHelper" so you can get the configuration parameters of each cluster (local config and remote config)

v0.6.3.0
- Added support for Apache Cassandra version 0.6.3.0

v0.6.2.1
- Change version to match Apache Cassandra version
- Fixed DeleteCommand validation exception when column value is null

v1.0.0.1
- Fixed divide by zero in SizeControlledConnectionPool.controlIdleClientSizeMethod

v1.0.0.0
- Initial Release that support Apache Cassandra version 0.6.2
- Connection Pool: to avoid performance and resource problems under heavy traffic.
- Node Balancing for proper distribution of traffic: this will equally distribute the connections to a cluster between all the nodes configured to that cluster.
- Defensive node health check: when the framework detects a node is down, it will ban that node and every X seconds will attempt to connect to it. When this try success then that node is put back in the distrubution list.
- Command Validation: Before attempting to open a connection against a cluster, Aquiles will validate the Command Input (Column, SuperColumn, etc). It even will validate that the ColumnFamily exists within the KeySpace, and that the KeySpace exists within the cluster.

Updated Wiki: Home

javiercanillas — Thu, 27 Oct 2011 13:27:27 GMT

News

Check download section, new support for 1.0. Documentation still not updated, it will be soon.
Follow us on tweeter to get updates @Aquiles4Net

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Instructions on how to enable this feature are in Aquiles.Diagnostic.Extension.

(*) This feature was disabled on last refactor, it will be enabled back again soon.

You can take a look at Version History for the lastest updates.

Commands Supported

Aquiles supports all the Cassandra commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

Suppose that you have a Cassandra instance configured in your App.Confg or Web.Config, and you named it "Cassandra1". Suppose then, that there is a Keyspace called "TestKeyspace" and within that KeySpace there is a ColumnFamily called "TestColumnFamily".
Now, lets presume that you need to insert a new key "testKey" with a new Column called "testColumn" with a value of "testValue". You may acomplish that with the following code.

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Core.Configuration.AquilesConfigurationSection,Aquiles.Core"/>
  </configSections>

Note: That the section name must be ''aquilesConfiguration'' and no other, or you Aquiles will not load and will throw a ConfigurationException when first time used.

After that, you will only need to configure your cluster's information like following:

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Q: Is this thing production ready?
A: Yes, im using it now on a heavy traffic site and it works great.

Q: Sure it is production ready?
A: Well, do a load test and give us feedback. If you find something wrong, let us know. And if you fix it, consider sharing the code.

Q: Are you going to support AVRO?
A: Maybe. At this time, the evolution of aquiles is driven by our needs, and we won't upgrade our cassandra servers until the TTL is on the trunk (or any other compelling feature or killing bug).

Q: Hey, it is Achilles!
A: Well, not for us spanish speaking people. To be fair, it should be Ἀχιλλεύς

Q: I'm a bit confuse on your version numbers. How do you choose them?
A: Well, yeap. I know it's a bit confusing. Cassandra now have 3 version numbers: Major.Minor.patchLevel. Well, I have added 1 more version lvl to the end in order to properly detect what is the release we are talking about. Besides this, and since Cassandra does not change its Thrift interface too much, you will probably just need the Aquiles that match exactly the first 2 levels of version (those would be just Major.Minor). For example: Aquiles 0.7.0.X can support from Cassandra 0.7.0.0 to 0.7.6.0 and so on. If you need further assistance just ask on the discussion section.

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

As you know, this project is free and it is supported and developed during my free time. However, I accept donations to help support Aquiles and accelerate development on it. Click here to donate to Aquiles

Updated Wiki: Home

javiercanillas — Thu, 27 Oct 2011 13:27:06 GMT

News

Check download section, new support for 1.0. Documentation still not updated, it will be soon.
Follow us on tweeter to get updates @Aquiles4Net

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Core.Configuration.AquilesConfigurationSection,Aquiles.Core"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Home

javiercanillas — Thu, 27 Oct 2011 13:26:48 GMT

News

Check download section, new support for 1.0. Documentation still not updated, it will be soon.
Follow us on tweeter to get updates @Aquiles4Net

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Core.Configuration.AquilesConfigurationSection,Aquiles.Core"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Aquiles.VersionHistory

javiercanillas — Thu, 27 Oct 2011 13:22:12 GMT

Version History

Planning changes
- using individual pools for each Keyspace connected from a cluster, doing so we avoid a roundtrip to set such keyspace on the connection before using it.

v1.0.0.0
added support for Cassandra 1.0.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.8.0.1
added support for Cassandra 0.8.X versions.
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v0.7.0.8
default unixtimestamp multipied by 1000 to standarize with cassandra-cli.
moved previous version to use inner Thrift generated Cassandra classes instead of external assemblies.
fix for workitem:14319 "DefaultCluster will attach a non detached connection when executing an ExecutionBlock"
moved Aquiles for Visual Studio 2010 and fwk 4.0 in order to use its new features.
moved to use Nuget as dependency version management.
moved to use Interlocked for better concurrency handling on SizeControlledClientPool.

v.0.7.0.6
- Added AquilesKeyRange the properties: StartToken and EndToken
- Changed the converter to support these new properties
- Added a GetKeyRangeSliceCommandTest method to test this new approach.
- 2 new encoders for Long (Big-Endian and Little-Endian). Please use these if you need to use the columns for second indexes. Use Big-Endian implementations for most of Cassandra versions, since Java default implementation of Long to ByteArray (and viceversa) is Big-Endian.
- moved Logging namespace to Diagnostics
- Added an Interface to support MonitoringFeatures (like time on borrows, releases, quantity of active connections, inactive connections and so on)
- Added a Helper to support the above feature internally
- Added a new property on the configuration section to be able to add your own implementation of IMonitorFeatures to log such information
- Added a whole new project that use PerformanceCounterHelper (see http://perfmoncounterhelper.codeplex.com) to submit the collected features values into Performance Counter.

v0.7.0.5
- fix GetKeyRangeSliceCommand doesn't support for empty Start and End Key
- Also fix that AquilesTokenRange structure to match Cassandra structure
- Modified RetrieveKeyspaceDistributionComand to return a list of AquilesTokenRange.
- added KeyspaceConnectionPool to avoid 1 roundtrip to Cassandra Cluster. Still on test!!!
- fix AquilesColumn has TTL as required, but it is optional in Cassandra
- fix UnavailableException and TimedOutException is not meaning of connection broken

0.7.0.4
- added a new ColumnFamily with TimeUUID comparator.
- SizeControlledConnectionPool: now throws an exception if the cluster has no valid endpoints when creating a new connection
- DefaultAquilesCluster: taking out the validation on the endpoints to assure they al point to the same cluster due to some problems when 1 endpoint is taken down after creating connection pool.
- Added support for "getindexedslices" that let you do a search with some conditions.

0.7.0.3
- Added Validation for TTL of Columns when inserting a column
- Added DateTimePrecise from http://www.codeproject.com/KB/cs/DateTimePrecise.aspx?display=Print to properly generate random Guid based on a more precise time data.
- Added a UUIDEncoderHelper that actually works with dotnet GUID but it converts to a byte[] structure compatible with Java UUID.
- Added Test for the above implementations and changes.
- fixed the UnixTimestamp. There was a bu* moved from Cassandra 0.7-beta2 to 0.7-beta2
- moved from thrift 0.2 to 0.5
- removed RenameColumnFamilyCommand and RenameKeyspaceCommand since they are not longer supported on Thrift API
- Optional properties on AquilesColumnFamily are now nullable to support default values within Cassandra Server.
- Added support for optional parameters on AquilesColumnFamilyConverterg that the actual DateTime was taken as UTC but the unitStartDateTime was not represented as UTC.
- Extended the TTL validation. It shouldn't let TTL value equal or below to zero.

0.7.0.2
- taken out all the keyspace and columnfamily validation since Cassandra 0.7.0-beta1 work with this on the fly
- Thrift structure converters created.
- changed command logic when creating and updating data to use converters.
- The GetKeyRangeSliceCommand threw a null reference exception when building output response. Fixed by Aaron8498.
- expose CfDef metadata in describe_keyspaces (CASSANDRA-1633)
- rename RackAwareStrategy to OldNetworkTopologyStrategy, RackUnawareStrategy to SimpleStrategy, DatacenterShardStrategy to NetworkTopologyStrategy, AbstractRackAwareSnitch to AbstractNetworkTopologySnitch (CASSANDRA-1392)
- remove keyspace argument from multiget_count (CASSANDRA-1422)
- Add AquilesColumnFamily.DefaultValidationClass (CASSANDRA-891)
- Add DescribeSplitsCommand to support describe_splits
- rename checkschemaagreement to describeschemaversions (CASSANDRA-1478)
- min, max compaction threshold are now configurable and persistent per-ColumnFamily (CASSANDRA-1468) (AquilesColumnFamily.MinimumCompactationThreshold and AquilesColumnFamily.MaximumCompactationThreshold)
- Removed Clock structure (CASSANDRA-1501)
- Added DescribeSnitchCommand to support new method describe_snitch in Thrift API (CASSANDRA-1490)
- v0.7.0.0-beta1
- Added preliminar support for Apache-Cassandra version 0.7-beta1

v0.6.4.2
- Moved SuperColumn Name and Columns names and values into Byte[]. Doing so, predicates and everything related to them are moved to Byte[] too. This will enable users to work with Long, TimeUUID and even Serializable Objects than can be converted into a Byte[].
- Added some useful EncoderHelpers in order to help clients to overcode this big change.
- Added more helpful methods and class comments.
- GetKeyRangeSliceCommand will now output a list of GetKeyRangeSliceCommand.Out class that now has the Key as property.

v0.6.4.1
- BatchMutateCommand with SuperColumns over a Standard ColumnFamily fixed
- MultiGetSliceCommand without SuperColumn over a Super ColumnFamily Type fixed

v0.6.4.0
- Added support for Apache Cassandra version 0.6.4.0
- Added support for the new method "describe_partitioner" through a new command called "RetrievePartitionerCommand"
- Added an static method called "RetrieveInformation" to "AquilesHelper" so you can get the configuration parameters of each cluster (local config and remote config)

v0.6.3.0
- Added support for Apache Cassandra version 0.6.3.0

v0.6.2.1
- Change version to match Apache Cassandra version
- Fixed DeleteCommand validation exception when column value is null

v1.0.0.1
- Fixed divide by zero in SizeControlledConnectionPool.controlIdleClientSizeMethod

v1.0.0.0
- Initial Release that support Apache Cassandra version 0.6.2
- Connection Pool: to avoid performance and resource problems under heavy traffic.
- Node Balancing for proper distribution of traffic: this will equally distribute the connections to a cluster between all the nodes configured to that cluster.
- Defensive node health check: when the framework detects a node is down, it will ban that node and every X seconds will attempt to connect to it. When this try success then that node is put back in the distrubution list.
- Command Validation: Before attempting to open a connection against a cluster, Aquiles will validate the Command Input (Column, SuperColumn, etc). It even will validate that the ColumnFamily exists within the KeySpace, and that the KeySpace exists within the cluster.

Updated Wiki: Home

javiercanillas — Fri, 21 Oct 2011 22:38:36 GMT

Check download section, new support for 1.0. Documentation still not updated, it will be soon.

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Core.Configuration.AquilesConfigurationSection,Aquiles.Core"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Aquiles.Configuration

javiercanillas — Sat, 17 Sep 2011 14:29:53 GMT

Basic

Configure Aquiles in .NET environment is easy. You are used to work with config files all the time (*.config) that provides us this technology, understanding that for App.config we point to Win32 Applications and for Web.Config we point to AspNet Web applications.
To be able to work agains Aquiles / Cassandra we only need to follow the steps below:

1.- Add the apropiate section handler into our config file:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
   <configSections>
      <section name="aquilesConfiguration" type="Aquiles.Core.Configuration.AquilesConfigurationSection,Aquiles.Core"/>
   </configSections>

Note: That the section name must be aquilesConfiguration and no other, or you Aquiles will not load and will throw a ConfigurationException when first time used.

2.- After that, we need to declare the node "aquilesConfiguration" with the following structure:

<aquilesConfiguration>
   <loggingManager>Aquiles.Test.Logging.Logger,Aquiles.Test</loggingManager>
   <clusters>
      <add friendlyName="TestCluster1">
         <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED" />
         <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
            <cassandraEndpoints>
               <add address="localhost" port="9160"/>
            </cassandraEndpoints>
         </endpointManager>
      </add>
      <add friendlyName="TestCluster2">
         <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED">
            <specialConnectionParameters>
               <add key="minimumClientsToKeepInPool" value="20" />
               <add key="maximumClientsToSupportInPool" value="1000" />
               <add key="magicNumber" value="7" />
            </specialConnectionParameters>
         </connection>
         <endpointManager type="ROUNDROBIN" defaultTimeout="3000">
             <cassandraEndpoints>
               <add address="localhost" port="9160"/>
               <add address="darwin" port="9160" timeout="9000"/>
            </cassandraEndpoints>
         </endpointManager>
      </add>
   </clusters>
</aquilesConfiguration>

Now, lets take a close view for each of the nodes

Advance

Logging Manager

In case that you want to see what's happening inside this box, you may do it by implementing from LoggerHelper. Aquiles will use that class to create an instance of it and route all the logging information through it. Then, you only need to add the whole Type of your class in the config to let Aquiles properly instanciate it.
Note: If you put an invalid class, or the class is not found an Exception during Initialization will be thrown.

Monitoring Features

Since version 0.7.0.6, Aquiles support to hook an IMonitorFeatures class implementation from its configuration section to send all the health information into some repository. Natively, Aquiles supports, by using the library PerformanceCounterHelper, sending all such information into Performance Monitor that is built in Windows. To enable this feature, you will need to register the IMonitorFeatures implementation doing something like the following:

 <aquilesConfiguration>
    <monitorFeaturesType>Aquiles.Diagnostics.Extension.PerformanceCounterMonitor,Aquiles.Diagnostics.Extension</monitorFeaturesType>
    ...
 </aquilesConfiguration>

The following information will be then monitorized within the new Category Aquiles - Performance Counters:

Number of Active connections
Number of Free connections
Number of invalid connections
Number of created connections
Number of destroyed connections
Average Time on borrowing a connection from the pool, expressed in milliseconds.
Average Time on returning a connection to the pool, expressed in milliseconds.
Average Time on invalidate a connection to the pool, expressed in milliseconds.
Number of Active endpoints
Number of banned endpoints

Average Time on command execution, expressed in milliseconds.

Clusters

The node cluster, is basically a container for a collection of configured clusters, Here you can "add", "remove", "clear" any cluster previously defined in the Configuration Heriachy.

Add a cluster

If you want to add a cluster, after the "<clusters>" node, put and "<add " and start adding the following attribute information:

friendlyName: a friendly name to call this configured cluster within your application. Note that by this name you will need to reference this cluster.

<clusters>
      <add friendlyName="TestClusterX">
      ...
      </add>
</clusters>

Remove a cluster

Consider this scenario, you have got a master config file with a cluster defined for you all Web Applications in your root directory, now, in a child Web Application, you decided that you don't need that cluster anymore, then, knowing the friendly name of the cluster to be removed, you add a "<remove friendlyName='XXXX'>".

<clusters>
      <remove friendlyName="TestClusterX" />
</clusters>

Clearing all previous defined clusters

Ok, in the scenario that you want to get rid of all the previously defined clusters (because you want to start over with your application) you may add the following in your "<clusters>" node.

<clusters>
      <clear />
</clusters>

Connection

Within the connection node, you will find the following attributes:

poolType: Defines what type of pool to use. The actual valid values are:
- NOPOOL: will make a faked pool where actually no pool strategy will be used (each time you need a connection, a new connection is created and when you release it or invalidate it, the connection will be destroyed. See NoConnectionPool.
- SIZECONTROLLEDPOOL: will make use of SizeControlledConnectionPool. See class details on the pooling mechanism.
factoryType: Defines how what kind of protocol to use when creating new connections. The actual valid values are:
- DEFAULT: It use binary protocol over socket transport. See DefaultTransportConnectionFactory
- BUFFERED: It use binary protocol over buffered transport (This is faster than Default). See BufferedTransportConnectionFactory

As a child node, there is a "specialConnectionParameters", inside this node, you will need to add a list of key-values accordingly to the poolType and factoryType previously defined. So see each implementation to see what are the key that they need.

EndpointManager

The endpointManager node, will define which will be the manage strategy to use, and what are the associated endpoints for that cluster. The following attributes are required:

type: Type of endpoint manager to use. The actual valid values are:
- ROUNDROBIN: this strategy will cycle through all the endpoints define, giving a Round Robin alike mechanism when retrieving an endpoint to create a connection against to.
- defaultTimeout*: the default timeout value for all the endpoints, in case each one of these don't defined a particular one. Only int values greater than 0 are allowed.

Cassandra Endpoints

This node is a collection alike container that only supports the add operation. The attributes each add may have are the followings:

address: the address of one node of the Cassandra Cluster. It may have a DNS name or an IP.
timeout: the particular endpoint timeout. Only int values greater than 0 are allowed. This attribute is optional since you have the defaultTimeout.

Updated Wiki: Home

javiercanillas — Sat, 17 Sep 2011 14:28:42 GMT

Check download section, Huge refactor plus support for 0.8. Documentation still not updated, it will be soon.

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra 0.7 & 0.8 commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Core.Configuration.AquilesConfigurationSection,Aquiles.Core"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="FRAMED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Home

javiercanillas — Mon, 22 Aug 2011 21:15:14 GMT

Check download section, Huge refactor plus support for 0.8. Documentation still not updated, it will be soon.

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra 0.7 & 0.8 commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Configuration.AquilesConfigurationSection,Aquiles"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="BUFFERED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Aquiles.BestPractices

javiercanillas — Mon, 22 Aug 2011 21:00:18 GMT

Hints

On a performance demanded application, it is recomended to added the following call to its startup process in order not to penalize the first operation attempt against Aquiles.

AquilesHelper.Initialize();

When not borrowing a connection from the cluster, you let the cluster to decide when to open the connection to execute your command. By doing so, you actually enable a capability that has the Aquiles.Core.Cluster.Impl.DefaultCluster object to retry the command in case it detects that the exception caught might be raised by a closed port or a temporal disconnection. This is advice to do on most every situation and is the recommendation. For example:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

Although, there are situations that needs to be handled separately. On these cases, AquilesCluster has 3 methods: "Borrow", "Release" and "Invalidate" that will let you do what you need. Take in mind that "borrowing" a connection from a cluster detach it from its internal pool, so after executing such methods the client owns the connection. It is recommended not to close it and it should be taken back into the internal cluster pool by doing "release" if you think that the client is healthy or "invalidate" if you prefer to destroy it.

For production environments, it is recomended to use Aquiles.Connection.Factory.BufferedTransportConnectionFactory instead of Aquiles.Connection.Factory.DefaultTransportConnectionFactory because it will use a Buffer to hold the information before sending the command to the server. Doing so, you avoid several calls into your SO kernel, making a performance improvement.

Best Practices

If you are going to make several commands against a cluster, it is recommended that you prepare all the commands outside the scope of the opened connection, doing so you will minimize the time you are holding a connection from the pool. Therefore, on a performance demand scenario you will avoid opening a large number of connection. For example:

string CLUSTERNAME = "Cassandra1";
KsDef keyspaceDefinition = new KsDef();
keyspaceDefinition.Name = "exampleKeyspace";
keyspaceDefinition.Replication_factor = 1;
keyspaceDefinition.Strategy_class = "org.apache.cassandra.locator.SimpleStrategy";
keyspaceDefinition.Cf_defs = new List<CfDef>();
CfDef columnFamilyDefinition = new CfDef();
columnFamilyDefinition.Keyspace = keyspaceDefinition.Name;
columnFamilyDefinition.Comparator_type = "BytesType";
columnFamilyDefinition.Key_cache_size = 20000;
columnFamilyDefinition.Row_cache_save_period_in_seconds = 0;
columnFamilyDefinition.Key_cache_save_period_in_seconds = 3600;
columnFamilyDefinition.Memtable_flush_after_mins = 59;
columnFamilyDefinition.Memtable_throughput_in_mb = 255;
columnFamilyDefinition.Memtable_operations_in_millions = 0.29;
columnFamilyDefinition.Name = "exampleCF";

ICluster cluster = AquilesHelper.RetrieveCluster(CLUSTERNAME);

ExecutionBlock describe_keyspaces = new ExecutionBlock(delegate(CassandraClient client)
{
    return client.describe_keyspaces();
});

List<KsDef> keyspaceDefinitions = (List<KsDef>)cluster.Execute(describe_keyspaces);
bool keyspaceExists = false;
bool columnFamilyExists = false;
if (keyspaceDefinitions != null)
{
    foreach (KsDef ksDef in keyspaceDefinitions)
    {
        if (ksDef.Name.CompareTo(keyspaceDefinition.Name) == 0)
        {
            keyspaceExists = true;
            List<CfDef> columnFamilyDefinitions = ksDef.Cf_defs;
            if (columnFamilyDefinitions != null)
            {
                foreach (CfDef cfDef in columnFamilyDefinitions)
                {
                    if (cfDef.Name.CompareTo(columnFamilyDefinition.Name) == 0)
                    {
                        columnFamilyExists = true;
                        break;
                    }
                }
            }
            break;
        }
    }
}
try
{
    if (!keyspaceExists)
    {
        ExecutionBlock create_keyspace = new ExecutionBlock(delegate(CassandraClient client)
        {
            return client.system_add_keyspace(keyspaceDefinition);
        });
        cluster.Execute(create_keyspace);
    }

    if (!columnFamilyExists)
    {
        ExecutionBlock create_columnFamily = new ExecutionBlock(delegate(CassandraClient client)
        {
            return client.system_add_column_family(columnFamilyDefinition);
        });
        cluster.Execute(create_columnFamily, keyspaceDefinition.Name);
    }
}
finally
{
    ExecutionBlock drop_keyspace = new ExecutionBlock(delegate(CassandraClient client)
    {
        return client.system_drop_keyspace(keyspaceDefinition.Name);
    });
    cluster.Execute(drop_keyspace);
}

Tricks

When using Aquiles.Connection.Factory.BufferedTransportConnectionFactory, if you want a good performance tune, consider adjusting the buffer size to a number accodingly to the average object size you are putting into that cluster, doing so you will hold the command in memory till its is ready to be transmitted. Be careful of this Trick, since a too large buffer size will eat up a lot of memory.

Updated Wiki: Home

javiercanillas — Mon, 22 Aug 2011 20:52:07 GMT

Check download section, Huge refactor plus support for 0.8. Documentation still not updated, it will be soon.

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra 0.7 & 0.8 commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Configuration.AquilesConfigurationSection,Aquiles"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="BUFFERED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Home

javiercanillas — Mon, 22 Aug 2011 20:50:29 GMT

Check download section, Huge refactor plus support for 0.8. Documentation still not updated, it will be soon.

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
a simple and user-friendly configuration section to configure all your clusters and support for dependency-injection frameworks.
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID, Long, Int and so on).
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk (*). Take the following screenshot as an example:

Commands Supported

Aquiles supports all the Cassandra 0.7 & 0.8 commands. Check Cassandra API on documentation about each one.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(i);
ColumnParent columnParent = new ColumnParent();
Column column = new Column() {
    Name = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Timestamp = UnixHelper.UnixTimestamp,
    Value = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue),
};

columnParent.Column_family = columnFamily;

ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
cluster.Execute(new ExecutionBlock(delegate(CassandraClient client) {
    client.insert(key, columnParent, column, ConsistencyLevel.ONE);
    return null;
}), keyspace);

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
byte[] key = ByteEncoderHelper.LongEncoder.ToByteArray(2);
ColumnPath columnPath = new ColumnPath()
{
    Column = ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName),
    Column_family = columnFamily,
};
ICluster cluster = AquilesHelper.RetrieveCluster("Cassandra1");
object rtnValue = cluster.Execute(new ExecutionBlock(delegate(CassandraClient client)
{
    return client.get(key, columnPath, ConsistencyLevel.ONE);
}), keyspace);

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Configuration.AquilesConfigurationSection,Aquiles"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="BUFFERED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Home

javiercanillas — Tue, 21 Jun 2011 00:46:37 GMT

Check code, Huge refactor plus support for 0.8. Take in mind that is still on development! Any criticsm do it on Discussions please!

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
- Input Parameter Completeness (no more going against a cluster to detect that you are missing a parameter!)
~~Prior Keyspace and ColumnFamily existance validation against a cluster information (retrieved on initialization)~~ (taken out since version 0.7.X)
a simple and user-friendly configuration section to configure all your clusters
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies using Aquiles (since version 0.7.X)
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID and soon on).
Fully support on GetIndexedSlices click here*
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk. Take the following screenshot as an example:

Instructions on how to enable this feature are in Aquiles.Diagnostic.Extension.

You can take a look at Version History for the lastest updates.

Commands Supported

Aquiles supports all the Cassandra 0.7 commands. Below you will find the most commons (check code for the full list):

System commands:

Note: Command help pages are under development.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
InsertCommand insertCommand = new InsertCommand();
insertCommand.ColumnFamily = columnFamily;
insertCommand.Key = key;
insertCommand.Column = new Aquiles.Model.AquilesColumn() 
    { 
        ColumnName = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName) , 
        Value = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue) 
    };

    using (IAquilesConnection connection = AquilesHelper.RetrieveConnection("Cassandra1", keyspace))
    {
        connection.Execute(insertCommand);
    }

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
GetCommand getCommand = new GetCommand();
getCommand.Key = key;
getCommand.ColumnFamily = columnFamily;
getCommand.ColumnName = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName);

using (IAquilesConnection connection = AquilesHelper.RetrieveConnection("Cassandra1", keyspace))
{
    connection.Execute(getCommand);
}

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Configuration.AquilesConfigurationSection,Aquiles"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="BUFFERED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Home

javiercanillas — Thu, 05 May 2011 21:22:29 GMT

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
- Input Parameter Completeness (no more going against a cluster to detect that you are missing a parameter!)
~~Prior Keyspace and ColumnFamily existance validation against a cluster information (retrieved on initialization)~~ (taken out since version 0.7.X)
a simple and user-friendly configuration section to configure all your clusters
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies using Aquiles (since version 0.7.X)
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID and soon on).
Fully support on GetIndexedSlices click here*
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk. Take the following screenshot as an example:

Instructions on how to enable this feature are in Aquiles.Diagnostic.Extension.

You can take a look at Version History for the lastest updates.

Commands Supported

Aquiles supports all the Cassandra 0.7 commands. Below you will find the most commons (check code for the full list):

System commands:

Note: Command help pages are under development.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
InsertCommand insertCommand = new InsertCommand();
insertCommand.ColumnFamily = columnFamily;
insertCommand.Key = key;
insertCommand.Column = new Aquiles.Model.AquilesColumn() 
    { 
        ColumnName = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName) , 
        Value = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue) 
    };

    using (IAquilesConnection connection = AquilesHelper.RetrieveConnection("Cassandra1", keyspace))
    {
        connection.Execute(insertCommand);
    }

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
GetCommand getCommand = new GetCommand();
getCommand.Key = key;
getCommand.ColumnFamily = columnFamily;
getCommand.ColumnName = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName);

using (IAquilesConnection connection = AquilesHelper.RetrieveConnection("Cassandra1", keyspace))
{
    connection.Execute(getCommand);
}

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Configuration.AquilesConfigurationSection,Aquiles"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="BUFFERED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All in Despegar)

Donations

Updated Wiki: Home

javiercanillas — Thu, 05 May 2011 13:46:26 GMT

Description

Aquiles is a .NET (v3.5 or above) Client for Apache Cassandra version 0.6.X or above using Thrift API.

Basically, It adds:

A .NET friendly interface to cassandra operations. You operates against cassandra as you would operate against an SQL (See examples)
Connection Pool with warm-up and size control capabilities
An Endpoint Manager to manage all the entrypoint nodes to one cluster. It will automatically distribute the connections against all the cluster endpoints defined, and will check for healthiness of the nodes with a defensive node health check strategy.
Command parameter Validation:
- Input Parameter Completeness (no more going against a cluster to detect that you are missing a parameter!)
~~Prior Keyspace and ColumnFamily existance validation against a cluster information (retrieved on initialization)~~ (taken out since version 0.7.X)
a simple and user-friendly configuration section to configure all your clusters
You can handle more than 1 cluster in your application
You can configure what ConnectionPool you want to use and its internal parameters.
You can choose what EndpointManager you want to use
You can choose what Transport do you want to use, and even when using TBufferedTransport you can set the length of the buffer!
You can managed (add, modify, remove) your Keyspaces and ColumnFamilies using Aquiles (since version 0.7.X)
Some Byte Enconder Helpers to avoid the need to create and managed your own (Long, UTF8, ASCII, GUID, UUID and soon on).
Fully support on GetIndexedSlices click here*
Monitor features out of the box, now you can monitor all your connections to Cassandra simply by using Performance Monitor (native with Windows) by implementing PerformanceCounterHelper fwk. Take the following screenshot as an example:

Instructions on how to enable this feature are in Aquiles.Diagnostic.Extension.

You can take a look at Version History for the lastest updates.

Commands Supported

Aquiles supports all the Cassandra 0.7 commands. Below you will find the most commons (check code for the full list):

System commands:

Note: Command help pages are under development.

Easy Example of use

Example 1:

string columnFamily = "TestColumnFamily";
string keyspace = "TestKeyspace";
string key = "testKey";
string columnName = "testColumn";
string columnValue = "testValue";

// Insert statement
InsertCommand insertCommand = new InsertCommand();
insertCommand.ColumnFamily = columnFamily;
insertCommand.Key = key;
insertCommand.Column = new Aquiles.Model.AquilesColumn() 
    { 
        ColumnName = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName) , 
        Value = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnValue) 
    };

    using (IAquilesConnection connection = AquilesHelper.RetrieveConnection("Cassandra1", keyspace))
    {
        connection.Execute(insertCommand);
    }

Example 2:

Now, Lets continue with the assumption of the Example1 and that you need to retrieve the value inserted. Your code would be similar to:

// Get statement
GetCommand getCommand = new GetCommand();
getCommand.Key = key;
getCommand.ColumnFamily = columnFamily;
getCommand.ColumnName = Aquiles.Helpers.Encoders.ByteEncoderHelper.UTF8Encoder.ToByteArray(columnName);

using (IAquilesConnection connection = AquilesHelper.RetrieveConnection("Cassandra1", keyspace))
{
    connection.Execute(getCommand);
}

As you see, using this client is, somehow, like using a connection to a Database (Cassandra is not a database, but the syntax is similar). More examples can be found at each command.

Aquiles Configuration Section

Configuring Aquiles to use a Cassandra cluster is easy, add the following section into your App.Config (Web.config in case of ASPNET application):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="aquilesConfiguration" type="Aquiles.Configuration.AquilesConfigurationSection,Aquiles"/>
  </configSections>

 <aquilesConfiguration>
    <clusters>
      <add friendlyName="Keyspace1">
        <connection poolType="SIZECONTROLLEDPOOL" factoryType="BUFFERED">
        </connection>
        <endpointManager type="ROUNDROBIN" defaultTimeout="6000">
          <cassandraEndpoints>
            <add address="localhost" port="9160"/>
          </cassandraEndpoints>
        </endpointManager>
      </add>
    </clusters>
  </aquilesConfiguration>

For further Configuration options, please see Configuring Aquiles

Hints, Tricks, Best Practices

See a list of Hints, Tricks and Best Practices in this document.

Frequently Asked Questions

Success Stories

Chirper: twitter clone WebApp with .NET front-end and Cassandra NoSql back-end (thanks Chaker Nakhli)
Common Information Platform: Common abstraction over various data stores. (thanks PatrickThompson)
Despegar.com: Online Travel Agency. (thanks All)