The Latest

2 Dec 2020: Salesforce introduces Hyperforce. This move is a re-architecture of Salesforce’s design to continually support its global customer base. It has B2B and B2C performance scalability, built-in security, local data storage, and backward compatibility.  

Hyperforce allows Salesforce solutions to be run on a hyper scale Cloud service based on the client’s choice. These solutions include:

  • Sales Cloud
  • Service Cloud
  • Community Cloud
  • Chatter
  • Lightning Platform (including Force.com)
  • Site.com, Database.com
  • Einstein Analytics (including Einstein Discovery)
  • Messaging
  • Financial Services Cloud
  • Health Cloud, Sustainability Cloud
  • Consumer Goods Cloud
  • Manufacturing Cloud
  • Service Cloud Voice
  • Salesforce CPQ and Salesforce Billing
  • Customer 360 Audiences

Why it’s Important

Being able to move a SaaS solution to the Cloud based on client's preference, is a radical departure from convention for most major SaaS vendors. It is likely to be followed by other SaaS solution vendors, though Oracle’s close ties with Netsuite and Microsoft Dynamics with Azure, suggest Salesforce’s two main rivals will not be following this strategy any time soon.

This is a long-overdue overhaul for the entire Salesforce architecture as it needs to offer both architectural and commercial elasticity to aid customer’s global digital transformation.

It solves data sovereignty issues and provides all the advantages of using public Cloud resources. It also reduces implementation time despite being an enhanced architecture designed from the ground up to help customers deliver workloads to the public Cloud of choice.

Who’s Impacted

  • CIOs
  • CTOs
  • CRM leaders
  • Salesforce developers

What’s Next?

While the Hyperforce announcement is welcoming, there are still loopholes in the horizon. The solution is not available for on-prem implementations of the major Cloud vendors. Meaning, Hyperforce is not a path to an on-prem or hybrid Cloud solution.

For Australian organisations that aim to gain more control over how Salesforce stores information, either for compliance or cost control, to bring it closer to other Cloud services, Hyperforce is worth considering. It offers greater flexibility but also comes with a greater need for managing resources and costs. 

Before making any decision on moving to Hyperforce, Salesforce clients should have clear understanding of the following migration aspects:

  • Who will do the migration (i.e. the client or Salesforce)?
  • Who will deal with the public IaaS provider on a daily basis?
  • How will the current service cost be impacted?
  • Who will be responsible for the service management of public IaaS including the service desk?
  • What are the new risks that should be identified and mitigated?
  • Are there any changes to the current backup arrangements?
  • Are there any changes to the disaster recovery and business continuity arrangements?
  • How will the current change management arrangements change?
  • How the exit fees might change?

Related IBRS Advisory