The GRAX solution is a Data Value platform that provides backup and archive functionality, as well as, advanced audit trail features to your data scenarios. GRAX is built with a core focus on Salesforce.com based data and data structures, allowing the offsite storage, management, and use of your valuable Salesforce.com data, as well as use with other non Salesforce platforms and services. Due to the nature of today’s cloud platforms, GRAX was designed to take advantage of 4 major technologies to achieve its value to any enterprise: Salesforce.com, Heroku, Elastic, and the most popular cloud storage providers.
Below is an overview of the GRAX ‘stack’, essentially, the 4 technologies that GRAX is built upon to achieve one, cohesive data value solution. It is essential to understand how GRAX utilizes these 4 core technologies, as the major areas of planning, installation, and implementation involve the configuration and management of each of these essential tiers of the GRAX solution (the ‘stack’).
Let's get into the core platforms and related components configured as part of the GRAX installation...
This serves as the user interface tier of GRAX. This tier is where the GRAX managed application is installed and is your main point of interaction with GRAX (user interface, job scheduling, archive, restore, etc.). Items for consideration and configuration consist of:
- GRAX managed package installation
- Permission sets, roles, and security
- Remote site settings
- Connectivity to the GRAX Heroku layer of the GRAX ‘stack’
- Validate availability of SF Connect (external data sources and connections) if using GRAX for advanced reporting and visualization (Einstein, standard reporting, etc.)
This tier serves as the core GRAX application or middle tier. This tier supports and manages the proxying of data bi-directionally between the GRAX data lake and Salesforce.com, the ability to scale elastically, manage dynos, resources, privacy, etc. Most of the configuration is managed at the Heroku layer of the GRAX app, as this essential middle-tier bridges the gap between Salesforce.com (the GRAX managed application/UI) and the GRAX data lake. Items for consideration and configuration consist of:
- SFDC user name, password, login URL and token for Heroku to Salesforce.com connectivity
- Storage credentials: key, secret key, region, bucket name
- Geographic regions for ‘where’ data can run and legally needs to reside
- Private space setup: setup, custom domain, VPC peering
- Need for Private Space ‘Shield’?
- Heroku resources to power GRAX: ensuring enough dynos / add-on credits to be able to performance tune GRAX effectively for the specific scenarios
This tier serves as the 1st part of the core data lake underlying technology for GRAX data lake storage. Elasticsearch indexes the most recent version of the SFDC data record for fast recall, search, and restore functions. GRAX uses this technology in cooperation with your chosen storage provider. You may choose to use the GRAX indexing or host your own Elastic Search.
We recommend hosting your own Elastic Search Instance on Bonsai. Grax will work with you during implementation to ensure proper configuration.
This tier serves as the 2nd part of the core data lake underlying technology for GRAX data lake storage. This tier serves as the primary data repository/long term storage for the data lake in that it contains all backup versions of records and the actual attachment binaries. Each storage provider has their own considerations which should be reviewed.
Additional items for consideration and configuration consist of:
- Additional considerations include:
- IP restrictions
- Any firewall rules
- Other security and access challenges or roadblocks
Updated 10 days ago