 My name is Syed Rashid. I'm the product marketing manager for JBoss DataGrid at Red Hat. Red Hat JBoss DataGrid is an in-memory data management system, which means it keeps all the data that an application requires in the memory instead of on the disk. That makes application works much faster. It can be used as a distributed cache, as a NoSQL database, as an event broker, and as an accelerator for IoT or big data solution. One of the critical problems that developers face is they can always add application servers to scale out their applications. But what about the data tier? How do you scale out the data tier? So that is one of the biggest bottlenecks. You can have multiple application servers, but they all go and attack the same database. With JBoss DataGrid actually provides a scale-out architecture for your data tier. So you can basically keep adding the node, and as your application scales out, your data tier scales out, and you get consistent high-performance applications. There's a saying that memory is the new disk, and disk is the old tape. So the idea is make your application work faster at the speed of memory. Your application runs inside the memory. So have the data that application requires also available in the memory so they can work at the same speed. Because most of the applications, disk.io is the biggest problem that impacts the application performance. Developers should use JBoss DataGrid if they want to build an application that provides superior user experience. What it means is it acts instantaneously. It provides instantaneous response times. It shows the data, it shows the information instantaneously. There is no lag, there is no delay, because nobody wants to wait. Nobody wants to use a slower application, and that's a key. We see this in a lot of industries where just one second lag in application response time or web application response time that can impact the conversion rate of how you convert your e-commerce browser. People who are just browsing your e-commerce site do bind from that site. So application response time, application experience is a key driver that developers should consider using JBoss DataGrid for. Yeah, so one of the new features we are introducing is support for Java Stream, which makes it very easy to develop highly parallel, high performance application. It's basically a simplified way to implement the results you get with MapReduce. So think about, you know, MapReduce was used to crunch very large datasets, build applications that are highly parallel, can work concurrently. Now what we are doing is, okay, you can do all those things, but using much simpler APIs, and not the learning curve that you otherwise incur learning how to do this in a MapReduce fashion. So it basically makes it a smoother learning curve because it's something that most of the Java developers are very familiar with. They can just use the API, they know how to do it. They don't have to rethink the, okay, I need to think in terms of a mapper and reducers and all that stuff. So it's a simplified way to implement MapReduce.