Chapter 12. Transactions
—Updated by Leonard Lobel and Kenn Scribner
Have you ever developed an application with the intention of writing unreliable code? Of course not. It would be equally absurd for a customer to appreciate the system you wrote that completely corrupted the customer’s data. Would you have much patience for a customer service representative who couldn’t help you because the information on the service representative’s computer wasn’t correct?
As absurd and exaggerated as these scenarios might at first appear, the fact remains that many software professionals treat the idea of writing reliable software all too casually. They concentrate most of their effort on getting the logic right and pay too little attention to ensuring that ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access