Apache Ignite is an in-memory computing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale. It can be used as an in-memory cache or as an in-memory database but that doesn’t mean everything has to move to Ignite. Users can keep their existing databases and deploy Apache Ignite on top of these data sources as a data caching layer that enables users to keep frequently accessed data in memory. We can also cache SaaS data sources like Salesforc or Oracle Sales Cloud for enabling high performance data processing, analytics and write to the source if we update the in-memory cache. Apache Ignite uses JDBC to integrate to relational databases and we can use this integration to cache our data with the help of Progress DataDirect’s JDBC Connector for Salesforce.
To get started, we will walk through how to connect and cache Salesforce data in Apache Ignite using the Progress DataDirect Connector for Salesforce.
java -jar PROGRESS_DATADIRECT_JDBC_SF_ALL.jar
On Linux
/home/<
user
>/Progress/DataDirect/JDBC_60/lib/sforce.jar
On Windows
C:\Program Files\Progress\DataDirect\JDBC_60\lib
On Linux
./ignite.sh
On Windows
.\ignite.bat
docker pull apacheignite/web-console-standalone
docker run -d -p 80:80 -v <
host_absolute_path
>:/var/lib/mongodb --name web-console-standalone apacheignite/web-console-standalone
We hope this tutorial helped import your Salesforce data to Apache Ignite cache for data processing, transactions, and analytics. Please contact us with any questions and we will be happy to help.