Hyperforce is Salesforce’s next-generation infrastructure architecture. It is a reimagining of the company’s platform architecture that was created to deliver the Salesforce Customer 360 safely and effectively. Salesforce aimed to create and provide the most pertinent solutions. They also sought to secure the organization’s related data while implementing and delivering the best practices currently used in the industry.
Redesigned from a ground-up structure, it allows Salesforce to continue innovating in production and service while scaling the product portfolio to new geographies on top of the public cloud infrastructure due to the growth and success of Salesforce’s global customer base. With the help of this service, Salesforce users will be able to use the public cloud’s scalability and agility to safely deploy Salesforce apps and services from any location in the globe.
Compliance – Hyperforce offers the possibility of keeping data locally while being compliant on a global scale – according to the country’s legislation. This enables you to adhere to rules that are exclusive to your business, area, or sector.
Scalability – with a highly adaptable architecture, Hyperforce enables you to build scalable features more quickly. Salesforce ensures capacity thanks to the ability to scale out infrastructure quickly.
Security – with Hyperforce, your data is safely protected. Salesforce keeps ranking as the number one CRM, and it is (partially) thanks to its well-protected and secure environment.
Compatibility – all these benefits listed above are backward compatible with how users experience today’s Salesforce, including how you make practical use of your organizations.
What does it offer?
- Performance at B2B and B2C scale: Customers will be able to readily get the computational resources required to be more flexible and efficient thanks to the public cloud’s elasticity. Resources may be deployed in the public cloud fast and simply with the help of Hyperforce, cutting the time required from months to just a few weeks or even days.
- Built-in trust: The security design of Hyperforce correctly restricts user access to client data, shielding critical data from human mistakes or configuration blunders. Data privacy and security are ensured through encryption, both in transit and at rest.
- Local data storage: Customers from all around the world may use Hyperforce to store data in a specified place to adhere to local, national, and international laws.
- Backward compatibility: No matter whether they are – cloud-based or not, Salesforce apps, customizations, and integrations will operate on Hyperforce.
Hyperforce’s Data Storage and Computing Limitations
Your Salesforce data storage and computing requirements are no longer constrained by the well-known limits of Salesforce orgs, thanks to Hyperforce. Through your own cloud or IT provider, you can scale up your gear and computing power.
Large-scale businesses can be greatly benefited from this – an extremely flexible, highly scalable choice, which will have no additional costs to customers.
Where is it available?
Bret Taylor, the CEO, and president of Salesforce stated that all major cloud providers will provide Hyperforce globally (AWS, for instance). However, your org has to internally pass some tests in order to be eligible for this migration, and at the same time, you need to ensure two criteria are met. Salesforce encourages its users that are interested in Hyperforce to be proactive with them to make sure they’re eligible for the migration.
Criteria to be able to migrate
The first criteria Salesforce looks for is the obligation to have My Domain enabled, being a required step. There are multiple benefits of having this enabled, besides being able to be eligible for Hyperforce: a single, customizable URL for your organization, social sign-on, and not having to worry about hard-coded URLs, which make the API integration process difficult (an important requirement for lightning components and email templates URLs).
Secondly, your request must not use the HTTP 1.0 protocol. It was introduced over 25 years ago and refreshed to Http 1.1 a year later. This protocol provides a basic security authentication since it exchanges login credentials in an unencrypted manner. It creates a TCP connection for every request, this way adding processing overhead and increasing latency. Salesforce is concerned due to the server dedication it requires. For now, though, its deprecation and future use in our CRM are still being debated, however, at the moment it is excused for the migration to Hyperforce.
Another important aspect to look out for is hard-coded references. They are any URL that contains a reference to a specific Salesforce instance – relevant for the reason that when carrying out a migration, the org instance names may change, thus affecting the integration and anything that relies on it. To fix this, Salesforce recommends updating your URL references by resources internally within your org, as well as external references to your organization
Some other recommendations from Salesforce are allowing the listing-required domains and enabling Tenant-Specific OAuth Endpoints.
In order to ensure compatibility with how HTTPS certificates are served, Salesforce is going to apply minor tweaks to Server Name Indication (SNI). With this improvement, some Salesforce users might have to do some additional preparation changes in order to be ready for the migration, due to the fact that in Hyperforce each feature domain uses a separate HTTPS certificate.
As explained above with the HTTP 1.0, in this case, some older API clients might not include SNI in their TLS ClientHello messages, a requirement for Hyperforce. The good thing is that nowadays most web browsers already include it, instead of using API clients to do it.
What to expect on the day of the migration?
The migration process is not much different from any other you might be familiar with – most probably, the administrator is going to receive an alert that the migration is going to begin any time soon. Thirty minutes before the maintenance starts, your org will be put into read-only mode. Any visitors to communities, portals, or sites will see a «Maintenance is in progress» message.
The duration of the migration is approximately 3 hours. Once the migration is complete and the tests to verify the sufficiency of the migration, the org will exit read-only mode and full functionality will be restored.
In the unlikely event of something going wrong, your org will go back to its original instance with normal functionality. Shortly after, you will be contacted by salesforce, communicating that the migration was not successful and the migration will be scheduled for a later date.
Salesforce recommends running pre-and-post-migration checklists in order to ensure full functionality, as well as unsubscribing from previous trust notifications.
Hyperforce is a great tool that has the potential to change the game for many Salesforce users around the world, enabling them to work with Salesforce in regions where it was not easy to do before. Salesforce clients are now able to use public cloud infrastructure to host their Salesforce instances, which allows Salesforce to compete with other big CRM firms like Oracle and Microsoft. This is made possible via Hyperforce, where you now can have full control over where your Salesforce data is stored.
The migration process is smooth and nothing out of the ordinary. Although you have to meet some requirements before you can be eligible, if your org is well-kept and updated, this shouldn’t really be a problem.