Transactional Models & Their Storage Requirements - ERP Spain.com - España y América Latina

We’re all accustomed to transferring money from one bank account to another; a credit to the payer becomes a debit to the payee. But that model uses a specific set of sophisticated techniques to accomplish what appears to be a simple transaction. We’re also aware of how today we can order goods online, or reserve an airline seat over the Internet. Or even simpler, we can update a photograph on Facebook. Can these applications use the same models, or are new techniques required? In this webcast, we’ll explore concepts like consistency, idempotency, 2 phase commit, and systems built on ACID databases stored on CRUD storage; and why in the age of distributed systems, we need to update our thinking to include eventual consistency, understand new theories such as the CAP Theorem and RESTfulness, and undertake transactional work in the face of unreliable and physically dispersed systems. We’ll then explain how all this can be accomplished with new application techniques built on modern storage systems. And yes, we’ll explain all the acronyms and nomenclature too. You will learn: •A brief history of transactional systems from banking to Facebook •How the Internet and distributed systems have changed and how we view transactions •An explanation of the terminology, from ACID to CAP and beyond •How applications, networks & particularly storage have changed to meet these demands