What Is ACID and Why Use It?

ACID stands for four traits of database transactions:

Atomicity - An operation either succeeds completely or fails; operations do not leave incomplete data in the system.

Consistency - Once an operation completes, the results of that operation are visible to every subsequent operation.

Isolation - Operations completed by one user do not cause unexpected side effects for other users.

Durability - Once an operation is complete, it will be preserved even if the machine or system experiences a failure.

These behaviours are mandatory to ensure transaction functionality.

If your operations are ACID compliant, the system will ensure your processing is protected against any failures.

Phoenix Kakfa Integration {Kalyan Contribution to Apache}

Hi All,

Phoenix Kafka is new Integration. You can follow the below link

http://phoenix.apache.org/kafka.html

This is new feature, require now a days .. 

Real time Streaming data pushing into OLTP system like Phoenix.

You can see similar use cases in below links from my blog.

Flume Real Time Projects

http://kalyanbigdatatraining.blogspot.com/p/learn-flume-from-basics-step-by-step.html

Kafka Real Time Projects

http://kalyanbigdatatraining.blogspot.com/p/learn-kafka-from-basics-step-by-step.html

How to track the `Production Level of Tracking` for any issues, like below

https://issues.apache.org/jira/browse/PHOENIX-3214

Please share to you friends & colleagues to know more on these kind of use cases.