By Michael Gleason, director of product marketing at OneLogin
Fun fact: in 2006, Forrester Research estimated that 90 percent of CRM sales were on-premises instances. That means ninety percent of CRM users had to deal with more than just a messy customer database – they had to deal with the hosting, the humans and the hardware necessary to host the application. In 2006, Salesforce.com’s trailing twelve month revenue wasn’t anything to scoff at – it was nearing half-a-billion dollars. Today, of course, that figure is more like $14bn.
Change is constant. As Heraclitus wisely explained 2,500 years ago: “No man ever steps in the same river twice, for it’s not the same river and he’s not the same man.” Often, replacing aging on-premises applications with Software-as-a-Service (SaaS) alternatives makes sense. Think Oracle CRM vs. Salesforce.com. Go find a head of marketing that wants to replace their Salesforce instance with Oracle CRM. I’ll wait.
Sometimes, there isn’t a suitable cloud alternative to an on-prem app. Or the change management of replacing an on-prem app with a cloud app is not worth tackling quite yet. Or incredibly complex internal workflows are dependent on these on-prem apps. Think Oracle eBusiness Suite. Or Peoplesoft. Or an on-prem instance of JIRA or Confluence.
If you can’t take some of these apps to the cloud, what if you can take the cloud to them? This philosophy is gaining traction, as seen in developments like Amazon Outposts, where users can run AWS infrastructure on-premises with an integrated hardware rack that runs native AWS or VMware environments to connect to Amazon’s public cloud. The problem with some legacy apps, despite their robust functionality and ..
Support the originator by clicking the read the rest link below.
