AWS Re:Invent 2013

If you missed the event on big data at AWS you may find it here.

Hadoop Summit 2013

Hadoop has matured from version 1.0 to version 2.0 and the research and contributions by some of the companies like Yahoo, Hortonworks, MapR, Cloudera, Spulk, Wandisco, Qubole, Teradata etc. has been quite phenomenal. These are the revolutionaries we should thank for providing us with solutions that enable us to solve the challenges with growing data at an unmanageable scale.

Click here to watch the video list.

C* Summit 2013 :: Evolving NoSQL DB

C* (cassandra) has grown pretty good overcoming challenges from version 1.0 to version 2.0 with the CQL 3.0 upgrades. Lets look at some of the new features, challenges, best practises and learn from our peers at the Cassandra summit 2013. Watch these videos at your leisure.

AWS Global Summit 2013

If you have missed the AWS global summit 2013, sit back and watch these videos.

DataStax DevCenter -- limitation

Installed DevCenter to notice that it is not possible to execute and run just one statement (by selecting the line) without commenting out other statements in the CQL Script file. ##calls_for_imporvement_in_tool

Strata 2013 :: Orielly's Summit on Data

I personally like the quality of this conference and as time passed, this conference gained more traction and the contents of this conference raised the bar but confined to absraction at some levels. I enjoyed watching this conference sitting at my home, i hope you can englighten yourself with some knowledge as well.

##Patent Idea, Multi-Channel Parallel Synchronous/Asynchronous replication

In distributed systems, everyone is familiar with synchronous replication and asynchronous replication process. When payload is written to a particular node, replication gets kicked in either in a sequential manner (synchronously) replicating one node after another node or in a silent (asynchronous) manner replicating bits and pieces on one or multiple nodes.

My idea is to propose an intermediate "replication manager" which manages/negotiates with the associated replicating nodes. The manager performs synchronous / asynchronous replication by opening multi-channel port connectivity to the replicating node to move the data in parallel multi-threaded faster mode depending on the resources availability. This should yield in faster replication than the traditional one connection replication. If the resources are busy, this mechanism falls into one connection mode.