From the course: Microsoft Azure Data Engineer Associate (DP-203) Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Regress to a previous state

Regress to a previous state - Azure Tutorial

From the course: Microsoft Azure Data Engineer Associate (DP-203) Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Regress to a previous state

“

- [Instructor] Now, this brings, again, to the forefront, some design decisions with regard to your emphasis on data consistency and transactional consistency. How are you going to allow for rolling back data to a stable state? Classic example is a banking application where a customer's going to perform a transfer, which consists of two operations, doesn't it? There's a withdrawal... Let me actually bring out my drawing tools here. You've got your withdrawal step and then you've got your deposit. And hopefully, it makes sense that if the withdrawal completes but the deposit fails, you need both of these operations to roll back or commit 100%. See? So that's the business case of transactions and rollback support, and that's been part of the relational world forever, seemingly. It's a core part of the relational data model. However, NoSQL systems historically have not accounted for rollback. Again, 'cause the emphasis…

Contents