Technical Presentations About GridGain and Apache Ignite

The technical presentations below will help you understand, configure, and deploy the GridGain® and Apache® Ignite in-memory computing solutions. The presentations cover topics including in-memory computing, in-memory databases, stream processing, data lake acceleration, machine learning, deep learning, and how to apply these technologies and others to power your organizations’ digital transformation. These technical presentations have been developed and presented by GridGain in-memory computing experts.


When you add a distributed in-memory computing cluster to support existing systems or new APIs, you introduce additional moving parts that can be hard to track and troubleshoot for performance issues or failures.
This webinar discusses how an in-memory computing platform such as GridGain or Apache Ignite can modernize existing data lake architectures, enabling real-time analytics that spans operational, historical, and streaming data sets.
In this presentation, Apache® Ignite™ PMC Chair Denis Magda shares a checklist to consider for your Apache Ignite production deployments.
Learn how companies have added speed and scale to MySQL deployments for different use cases. This presentation will cover the various options available and when each option makes sense. It will also cover how to evolve your architecture over time to add the speed, scale, agility and new technologies needed for digital transformation and other initiatives.
As an in-memory computing platform, GridGain® and Apache Ignite support native persistence that stores data and indexes transparently on non-volatile memory, SSD or disk. This presentation provides insights into the underlying architecture and best practices for implementing native persistence in production.
Learn how companies have added speed and scale to PostgreSQL deployments for different use cases. This presentation will cover the various options available and when each option makes sense. It will also cover how to evolve your architecture over time to add the speed, scale, agility and new technologies needed for digital transformation and other initiatives.
In this presentation, Yuri Babak, the head of ML/DL framework development at GridGain and major contributor to Apache Ignite, will explain how ML and DL work with Apache Ignite, and how to get started. Topics include:
This presentation will show how to add speed and scale to your Oracle Database, Oracle-based applications, APIs and analytics for different use cases. It will discuss when each option makes sense, as well as how to evolve your architecture over time to add the speed, scale, agility and new technologies needed for digital transformation and other initiatives.
In this presentation, we will cover the specifics of how to use Node.js with Ignite, including:
This presentation will help you understand best practices about how to configure Ignite and GridGain for deployment, management and monitoring; leverage log files for troubleshooting, and fix and identify top errors in your deployment.
This presentation discusses the new features and functionality of Apache Ignite. Topics covered include: Transactional SQL Deep learning with TensorFlow Thin client support for Node.js, Python, PHP Transparent encryption for Ignite persistence
This presentation covers best practices for delivering new applications and APIs with in-memory computing, and how it helps open up existing systems, become more agile, and deliver unlimited speed and scale.
This presentation explains the best practices for adding speed and scale to existing applications that offer the least disruption and help meet the long term goals of transforming the business.
Learn how companies have been using Apache® Ignite™ to add in-memory speed and unlimited horizontal scale to SQL with no rip-and-replace of the underlying database. This session will explain how to:
technical_presentation thumbnail
This presentation covers some of the best practices companies have used for making Apache Ignite and Apache Kafka scale. Making stream processing scale requires making all the components—including messaging, processing, storage—scale together.