InfoQ Homepage Presentations An Introduction to Data Grids
An Introduction to Data Grids
45:25
Summary
Cameron Purdy explains how a data grid functions by using a partition topology for data access, update, recovery and local storage, accessing data using read/write-through and write behind, and invoking operations through Observable, QueryMap and InvocableMap interfaces. He also offers some examples of data grids solving complex problems and introduces Coherence, Oracle’s data grid solution.
Bio
Cameron Purdy was the founder and president of Tangosol, Inc, a market leader in delivering in-memory caching and data management solutions to companies building and running mission critical enterprise J2EE applications. He currently is VP of Development at Oracle.
About the conference
Jfokus is the largest annual conference for everyone who works with Java in Sweden. At Jfokus you will have an unique opportunity to keep yourself updated with the latest development of the Java platform through numerous interesting sessions. Jfokus gather rock-star speakers, both from Sweden and internationally. The focus is system development with Java and surrounding techniques like dynamic languages and agile methodologies. Jfokus is the best way for you to get the latest trends and buzz about Java from people who live and breathe technology on a daily basis.
Oct 10, 2009
Community comments
but the deep question is why don't developers get this
by Matthew Rawlings,
but the deep question is why don't developers get this
by Matthew Rawlings,
Your message is awaiting moderation. Thank you for participating in the discussion.
Cameron has been putting this straightforward message out for years in new and innovative ways. It is a few simple principles that are largely self-evident, with a proven track record, big examples, great successes, and a solid theory behind it. Distributed Systems got codified years ago. The only difficult question is just why developers don't understand this simple stuff.
My personal opinion is that people learn to code wrong from the beginning. They get taught to express logic by using sequences in code. Tthey use step through debugging. They expect each app to be in a separate VM/object space and never multiple and never shared. And then they expect to build a distributed system as just a bigger app, but it isn't.
Until we remove the things we can't rely upon in distributed systems away from the basic language, we won't end this thinking. i.e. sequence, identity of objects, locking, etc.