Generica is your average-sized company that has a handful of internally-developed applications. They’re facing challenges with an aging hardware setup, the costs associated with maintaining it, and the lack of scalability it comes with.
Generica has been running a few of its own applications on a small on-premise datacenter. The applications themselves are ideal for Generica’s needs, well-designed and well-liked amongst its employees.
Unfortunately the hardware it’s relying on to run them is aging rapidly, and costs to keep it at even sub-par performance levels are skyrocketing. The apps and Generica’s operations are suffering as a result, but outright replacing their infrastructure is both cost prohibitive and unsustainable.
Generica makes the decision to move to the cloud in order to gain currently absent scaling capabilities in addition to relieving itself of any future hardware maintenance liabilities.
With The conventional Cloud Solution
Since Generica doesn’t have prior experience administering cloud technologies it opts to engage a consultancy both to recommend a solution and eventually handle the migration.
The first report Generica receives from the consultants proposes 2 main options:
- Perform a simple “lift-and-shift” of their applications to a new cloud provider.
- Undertake a thorough rewrite of the apps to optimize them for the cloud.
Option 1 entails securing sufficient cloud infrastructure, spinning up a number of VMs, and then simply copying over the applications in their current state while adapting them for network setup and integrations. The main drawback here is that the applications would lose out on any dynamic scaling efficiencies offered by Generica’s new cloud infrastructure—which will inflate ongoing costs.
Option 2 enables Generica to leverage the best features and efficiencies of their new infrastructure, but requires a hefty upfront investment to rewrite the apps. They also need to contend with the risk for disruption to their operations when the new versions are pushed along with an inevitable host of new bugs.
The consultants also offer a third option involving a partial rewrite, but Generica is unconvinced that this hybrid approach is worth pursuing.
With a Cloudshift21 Cloud CapsuleTM
The options presented by Generica’s consultants would be appropriate for implementation on the company’s new Cloud CapsuleTM as well. But differences quickly arise in the amount of work needed to get the job done.
With a lift-and-shift, Generica could simply register for their Cloud CapsuleTM, log in, and directly import their applications into their new Workspace after they’ve packaged them into containers. They would be able to run them as-is immediately after the import was complete—no configuration or setup of a complex cloud environment is necessary.
When it comes to a cloud-native rewrite, the difference with a Cloud CapsuleTM is that it can be done in phases. The Workspace environment makes it easy to add functions and integrate them with the existing application logic little by little.
Not only would this actually eliminate the need for Generica to hire consultants in the first place, it would also provide an exceptionally cost-effective environment through which its own personnel would be able to gradually learn cloud development as they go.