You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram.
To start, here are three criteria from [...]
November 18, 2008
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good.
The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog is written by Doug Barry.
The phrase "all or nothing" succinctly describes the first ACID property of atomicity. When an update occurs to a database, either all or none of the update becomes available to anyone beyond the user or application performing the update. This update to the database is called a transaction and it either commits or aborts. This means that only a fragment of the update cannot be placed into the database, should a problem occur with either the hardware or the software involved.
Features to consider for atomicity:
a transaction is a unit of operation - either all the transaction's actions are completed or none are
atomicity is maintained in the presence of deadlocks
atomicity is maintained in the presence of database software failures
atomicity is maintained in the presence of application software failures
atomicity is maintained in the presence of CPU failures
atomicity is maintained in the presence of disk failures
There are nearly 400 pages of articles on this site with over 40 pages on database concepts and standards.
Search this site for more articles
Custom Search
Browse this site for more articles
Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current
article: Atomicity.
Related recent articles from Google News
SSDs Speed Up Online DBMS Performance NetworkComputing.com For a $35 monthly fee, customers receive access to detailed inventory data for more than 40 million components. They can determine what items different ... 19 Mar 2010 at 10:10am
Embedded controllers capture energy data Dataweek (press release) Once read, the values are normalised and written directly into a database management system (DBMS). The PC Worx automation software supports direct ... 16 Mar 2010 at 3:31am
Transaction Processing: Concepts and Techniques (The Morgan Kaufmann Series in Data Management Systems) by Jim Gray, Andreas Reuter Average Customer Review: based on 9 reviews. Customer Review: For nearly a decade this book has been the definitive reference on transaction processing. Although the more recent, May 2001 book titled "Transactional Information Systems: Theory, Algorithms, and the Practice of Concurrency Control" by Gerhard Weikum and Gottfried Vossen will probably supplant this book as the standard reference, t...
Database and Transaction Processing by Philip M. Lewis, Arthur Bernstein, Michael Kifer Average Customer Review: based on 4 reviews. Customer Review: Database and Transaction Processing by Philip M. Lewis, et al. is written as a multi-purpose textbook and practical reference guide for software engineers. One can use this book both as an undergraduate introductory course in database theory and design, as an advanced graduate-level course in databases, or as a graduate level course ...
Roger Jennings' Database Workshop: Microsoft Transaction Server 2.0 by Steven D. Gray, Rick A. Lievano, Roger Jennings Average Customer Review: based on 17 reviews. Customer Review: I purchased the book in order to get up-to-speed with MTS. Although it left some unanswered questions, the book lived up to its promise to get me up-and-running with MTS in a flash. Using the sample code as a basis, I built and deployed my first MTS app in a little less than a month. A follow-up book providing deeper insight into th...
Link code for page
based on 9 reviews.
based on 4 reviews.
based on 17 reviews.
based on 1 review.
