Meet Hyperforce, the groundbreaking infrastructure model set in motion by Salesforce to harmonize the foundations of varied Salesforce Clouds. With the power to deploy Salesforce instances across public clouds including AWS, Azure, and GCP, Hyperforce propels Salesforce’s expansion in new territories, efficiently catering to clients’ data residency and compliance obligations.
Key Attributes of Hyperforce
Hyperforce shines with its remarkable features designed to improve compliance, compatibility, security, and efficiency. Here’s how:
- Compliance and Regulation: Hyperforce prioritizes local data storage, promoting stringent compliance with regulations.
- Compatibility: From applications and customizations to integrations, all Salesforce elements are compatible with Hyperforce and offer backward compatibility.
- Security: Hyperforce assures superior data security, enforcing encryption both in transit and at rest.
- Infrastructure and Application Separation: For multi-cloud implementations, Hyperforce can uncouple infrastructure from the application, enabling the app infrastructure to reside closer to the client applications and users.
- Proximity: Merging Salesforce data with existing workloads, using external processing capabilities like Salesforce Functions, or integrating Salesforce data with various applications using MuleSoft, becomes significantly advantageous when Salesforce data resides in the same public cloud instance.
Hyperforce Architecture: A Deep Dive
Hyperforce is more than an innovative infrastructure model; it’s an intricate dance of infrastructure management between Salesforce and the public cloud providers. This balance allows Salesforce’s Lightning Platform to thrive over public cloud infrastructure.
The architecture of Hyperforce revolves around three essential principles:
- Immutable Infrastructure: Hyperforce stands on an immutable infrastructure. Servers, containers, or VMs are created once and updated by launching a new version and deprecating the old one, enabling predictable state and eliminating configuration drift.
- Multi-Availability-Zone: To ensure high availability, Hyperforce exploits the multi-availability zones of public clouds. This strategy facilitates the deployment of compute resources across numerous regions that function as a single system while retaining the reliability of distributed systems.
- Zero Trust: Hyperforce believes in zero trust. There is no implicit access to resources; all data, whether at rest or in transit, is encrypted. All request paths are authenticated and authorized explicitly, adhering to the principle of least privilege access.
Planning a Migration to Hyperforce?
Before you hop on the Hyperforce bandwagon, here are our top five factors to consider:
- Production Instance Migration: Hyperforce migrates only the production instance. If you have multiple sandbox instances, you’ll need to recreate or refresh them after the migration.
- Read-Only Access: During migration, your Salesforce org will switch to read-only mode. So, pause all Salesforce integrations during this period and ensure retry mechanisms are active.
- URL Update: Remove any hardcoded instance URLs and use my domain URLs. Enabling My Domain in your org is always a best practice.
- IP Range: Update allowed IP ranges to accommodate the new Hyperforce cloud ranges, especially if you have a network firewall based on IP ranges.
- HTTP Version: Ensure all integrations use HTTP/1.1 as Hyperforce does not support HTTP/1.0 requests.
Preparations for Org Migration
To ensure a seamless transition, Salesforce conducts an eligibility check on orgs before migration. These checks are done based on your Salesforce usage to determine if the org is ready for migration onto Hyperforce. Some of these checks involve identifying orgs using particular services or features not currently available on Hyperforce and keeping these orgs from migrating.
Enabling My Domain
Enabling “My Domain” is crucial for customers requesting an org migration. If you have any hard-coded references, ensure you update them to relative URLs before the org migration. My Domain also offers several key benefits such as personalized URLs, social sign-ins, and avoidance of hard-coded URLs for API integration. It’s best to test changes in sandbox first, communicate to users about the change, and make the modifications during non-business hours.
The Hyperforce Migration Timeline
The migration process to Hyperforce lasts approximately three hours. Importantly, the org is accessible only in read-only mode for 30 minutes before migration.
Best Practices for Org Migration
- Remove Hard-Coded References: Ensure that links within your application refer to instance-less URLs like https://login.salesforce.com
- Enable All Applicable Salesforce IP Ranges and Domains: For your integrations, Salesforce recommends allowing all Salesforce IP addresses and domains in your firewall filters.
Are you looking to experience the revolutionary shift that Hyperforce promises for your Salesforce instances? Or do you need assistance with Hyperforce migration? Don’t hesitate to contact us at email@example.com or through our LinkedIn page.