<<< Previous speaker Next speaker >>>

Jags Ramnarayan, GemStone

Jags Ramnarayan

As the Chief Architect for GemStone Systems, Jags is responsible for the technology direction for its high performance distributed data management infrastructure platform. He has been directly involved in guiding several large customers in adopting and successfully deploying high performance data architectures.

With more than 17 years of experience, Jags helped GemStone architect their J2EE application server platform embedding an object database as a core cache in the 90's. As the Web Services Architect for BEA, Jags represented BEA in the W3C SOAP protocol specification, JAXM and other standards. Jags has also represented GemStone in the J2EE platform specification and the EJB expert group in the past. He has presented in several conferences on high performance data management.

Presentation: "Panel Discussions: Architecting for Performance and Scalability"

Time: Thursday 11:00 - 12:00

Location: Rutherford Room

Abstract: TBA

Presentation: "Dramatic scalability for data intensive architectures"

Time: Thursday 14:30 - 15:30

Location: Rutherford Room

Abstract:

Increasingly today's data intensive applications have to deal with data from multiple data repositories, and aggregate this in real-time with streaming events (Rich e-commerce portals, electronic trading, web 2.0, grid centric applications like risk analytics, fraud detection, etc). Traditional architectures that use simple clustering and databases for state management and messaging solutions for sharing events are being replaced with a middle tier memory oriented data fabric or grid - a sophisticated caching infrastructure that provides most of the key semantics available in a ACID database along with the ability to continuously analyze flowing events and generate derived events at a predictably high rate.

We present a architecture along with concepts that address the following two issues:

  1. How do you provide instantaneous access to data that is changing rapidly, large in volume, shared by clustered applications that might be spread across a wide area network without incurring high latency due to disk access, high setup cost for high availability and data consistency issues with asynchronous publish-subscribe?
  2. How do you support thousands of concurrent clients that want to express complex interest on fast moving data and be notified reliably with predictable latency?

The presentation covers topics like data partitioning across a cluster, process-data affinity, dealing with data hotspots by repartitioning on the fly, dealing with computational hotspots by load conditioning and shedding techniques, etc. On event processing front, we talk about the new paradigm of "continuous querying" on partitioned data in memory.