Skip to main content

NoSQL BASE vs SQL ACID

SQL
http://www.postgresql.org/docs/8.4/static/explicit-locking.html#LOCKING-TABLES

Atomicity : all or nothing (rollback)
Coherence : coherent before, coherent after
Isolation: not impacted by others?
Durability : commit, if it's done, it's really done

Atomicity: tất cả hoặc không có gì (rollback)
Coherence: mạch lạc trước, mạch lạc sau
Cách ly: không bị ảnh hưởng bởi những người khác?
Độ bền: cam kết, nếu nó được thực hiện, nó thực sự thực hiện

http://stackoverflow.com/questions/4659422/locking-mysql-tables-rows

NoSQL
http://www.martinfowler.com/tags/noSQL.html

Basic Availability
    • The database appears to work most of the time.
Soft-state
    • Stores don’t have to be write-consistent, nor do different replicas have to be mutually consistent all the time.
Eventual consistency
    • Stores exhibit consistency at some later point (e.g., lazily at read time).

Comments

Popular posts from this blog

Rand mm 10

https://stackoverflow.com/questions/2447791/define-vs-const Oh const vs define, many time I got unexpected interview question. As this one, I do not know much or try to study this. My work flow, and I believe of many programmer is that search topic only when we have task or job to tackle. We ignore many 'basic', 'fundamental' documents, RTFM is boring. So I think it is a trade off between the two way of study language. And I think there are a bridge or balanced way to extract both advantage of two method. There are some huge issue with programmer like me that prevent we master some technique that take only little time if doing properly. For example, some Red Hat certificate program, lesson, course that I have learned during Collage gave our exceptional useful when it cover almost all topic while working with Linux. I remember it called something like RHEL (RedHat Enterprise Linux) Certificate... I think there are many tons of documents, guide n books about Linux bu

Martin Fowler - Software Architecture - Making Architecture matter

  https://martinfowler.com/architecture/ One can appreciate the point of this presentation when one's sense of code smell is trained, functional and utilized. Those controlling the budget as well as developer leads should understand the design stamina hypothesis, so that the appropriate focus and priority is given to internal quality - otherwise pay a high price soon. Andrew Farrell 8 months ago I love that he was able to give an important lesson on the “How?” of software architecture at the very end: delegate decisions to those with the time to focus on them. Very nice and straight-forward talk about the value of software architecture For me, architecture is the distribution of complexity in a system. And also, how subsystems communicate with each other. A battle between craftmanship and the economics and economics always win... https://hackernoon.com/applying-clean-architecture-on-web-application-with-modular-pattern-7b11f1b89011 1. Independent of Frameworks 2. Testable 3. Indepe