Skip to main content

CAP ACID noSQL


Probably due to the predominant position of a few actors (Google, Amazon, Facebook, etc.), I often feel that all I used to learn about small size systems will soon be obsolete.

The current fashionable IT word is noSQL. If you don't have a minimum of IT culture and only read the buzzy articles you could think the SQL thing is dead.
After a short analysis, I collected a few answers and mainly understood, both old and new technologies will have a long life, but their opposition really makes us step back and reconsider.

First, there is ACID for atomicity, consistency, isolation and durability, the properties implemented by the Database management system (DBMS) to make sure the transactions proceed reliably.

Most of the time we use databases of this type in our indoor computing system. But when it comes to distributed ones (many nodes) you've got to understand that a choice has to be made. In 2000, Eric Brewer made a keynote speech at the ACM Symposium on the Principles of Distributed Computing (PODC) about key principles in the name of CAP:
  • Consistency (all nodes see the same data at the same time)
  • Availability (node failures do not prevent survivors from continuing to operate)
  • Partition Tolerance (the system continues to operate despite arbitrary message loss)
I'm not going to explain what others have done greatly before so read
Sources:
Wikipedia : ACID
Wikipedia : Database management system
Nahurst : Visual Guide to NoSQL Systems
Kennygorman : Dropping ACID
Julianbrowne : Brewer's CAP Theorem
Highscalability : Drop ACID and Think About Data
Blip : Drop ACID and think about data

Comments

Popular posts from this blog

Learning about Data Science?

This is the end of a beautiful summer, and also one of the warmer recorded in France. I’m continuing my journey in the product management world and today I’m living in the product marketing one too. I will blog about this later. During this first half of this year, I read several articles on big data and started to understand how important the data science discipline is. Being able to define a direction/goal to search, collecting the proper data, then using a collection of techniques to extract something others can’t see - it sounds like magic. Also, when I listened to the Udacity Linear Disgression podcast episode “Hunting the Higgs”, I understood people with these skills can be better at solving a problem than the domain experts themselves. Katie Malone explained that in a competition to solve a particle physics problem, the best results came from machine learning people. Then I read the article about Zenefit on the vision mobile website : “Zenefits is an insurance compan

Lancement de ProductTank Lyon

Tout d’abord, bonne année 2020. Je me suis investi ces dernières années dans les communautés/événements CARA Lyon, MiXiTConf, LyonDataScience et CaféDevOps sur Lyon, France. Ces activités m’ont permis de comprendre les experts de ces domaines, d’apprendre quelques notions fondamentales à travers leurs exposés et d'améliorer mes capacités d’échange avec eux. Product Manager depuis plus de 5 ans, je désire améliorer mes réflexes et compétences dans mon domaine. Le faire à travers des rencontres/meetup est ce que je préfère et j’aimerais retrouver la stimulation des communautés dans cette discipline. En cette année 2020, quelques Product Manager Lyonnais, lançons, le meetup ProductTankLyon à Lyon, France. Le réseau ProductTank compte plus de 150 meetup dans le monde et profite des conférences, blog et podcast MindTheProduct. Inscrivez-vous ici , si vous voulez vous joindre à nous.

Read bead experiment

The "Read bead experiment" was created by Dr. Edward Deming and aim to demonstrate the ineffectiveness (sometimes effectiveness) of the various management methods. At the end of the experiment, a statistical graphical tool is used to analyse the experiment's results. By following this exercise, you will understand that actions taken by the people playing the managers are detrimental to the employees, but after the analyses are shown to have no impact on the efficiency of the process . The conclusion proposes ways to properly use performance data in a quality environment in order to achieve continual improvement. The several videos by Fluor Hanford (Steve Prevette) posted below, will help you to understand what is really important in a process. Meet the  company  with its "willing workers", quality control personnel, a data recorder, and a foreman. All wish to produce white beads using a 50 holed paddle, but unfortunately there are bad quality red beads.