NoSQL Immediate Data Consistency: Why and When is This Important?

The discussion whether NoSQL databases should be ACID compliant continues to surface. The core issue focuses on the problem of immediate vs. eventual data consistency. Many NoSQL systems support only an eventual (BASE) consistency, which is sufficient in some application domains. However, this form of data consistency is generally not appropriate for applications that require accurate data in real-time, where ACID compliance may be a better fit. These include, but are not limited to, financial, transportation, shipping and some manufacturing applications.

Therefore, one should always consider the question of how recent the usable data should be when deploying a NoSQL system. This presentation, led by Randal Hoff, vice president of Engineering Services at FairCom, will discuss the notions of immediate and eventual data consistency and examine several DBMS market segments that require immediate consistency vs. those for which the eventual consistency may be sufficient.

As FairCom's Vice President of Engineering Services, Randal Hoff overseas the technical support, training and overall product satisfaction of the FairCom customer base. Working directly with an advanced team of skilled engineers, Hoff keeps their focus on providing the best possible technical services for FairCom customers. His technical career, which spans more than 25 years, includes progressively responsible positions at FairCom and General Electric. Hoff holds Bachelor of Science degrees in Computer Engineering and Electrical Engineering from the University of Missouri, Columbia. When he's not coding: Hoff enjoys spending time with his family, including watching his daughter compete in college level golf tournaments and his son's college soccer matches.