Home Front end Why adopting the cloud doesn’t mean ditching your legacy technology

Why adopting the cloud doesn’t mean ditching your legacy technology



It is now widely accepted that cloud computing is not only the computing of the future, but is the most efficient computing at the moment in terms of easy deployment, flexibility and even cost.

The result is that most businesses over the past 5 years have moved to the cloud and are accessing all the applications they need through our public private clouds.

Forrester Research

The benefits of the cloud notwithstanding, it also leaves many businesses with many legacy applications that cannot be simply removed or terminated by many of them still play an important role in corporate or contact data reservoirs. that have not been migrated to the cloud.

Take the example of enterprise content management systems. According to the recent Forrester study Wave for content platforms The enterprise content management (ECM) market continues to evolve towards flexible and extensible cloud-centric platforms. While modern content platforms now dominate the vendor landscape, and customers continue a steady pace of migration to these platforms – away from aging on-premise repositories, we read in the wave, vendors with mature offerings have redesigned their platforms to take full advantage of cloud scalability.

On top of that, the research adds, new cloud providers continue to invest in advanced governance and automation capabilities. All vendors are embracing AI and ML to automate routine activities and creating design and development tools to help their customers deliver personalized user experiences and meet specific vertical requirements. In these circumstances, the future and use of existing applications is a key part of the digital transformation of many businesses.

Related Article: Why The Cloud Should Be Your Default Setting

Legacy technology planning

Most organizations have complex technology ecosystems that need to be audited, documented, and unraveled just to start planning a move. Therefore, the move to the cloud is not something to be rushed. Organizations need to take the time to plan properly to understand the results of all of their systems, Daniel Herndon, director of cloud services in Long Beach, Calif. Laserfiche, mentionned.

Not all software is the same, and understanding the priority of your systems is a great starting point for planning the future of existing systems. “Moving all of an organization’s technology to the cloud will take time, and the timing of the migration will help determine the future of existing systems,” he said.

Understanding the product roadmap of your legacy technology could reveal the future path to cloud migration. The introduction of a future cloud service may be part of the timeline of the organization’s larger migration strategy. Your software vendor may also offer attractive discounts to keep them, which offsets the expense of maintaining internal resources.

It is also possible that some legacy technologies never migrate to the cloud. Some systems handle sensitive workloads that must remain in the corporate network or must support integrations with sensitive systems. In these cases, web APIs can be used to integrate these legacy systems with cloud-based systems. So even if the technology is not available or cannot be supported in the cloud, there are still options available that allow these technologies to remain a vital part of the enterprise technology ecosystem.

“Migrating to the cloud is not an all-or-nothing proposition. There are many factors that determine a company’s cloud migration planning, strategy, and execution, and the current and future capabilities of a legacy technology should all be considered when making end-of-life decisions. life regarding your legacy technologies, ”he added.

Planning for cloud migration

Will Milewski is Senior Vice President of Cloud Infrastructure and Operations at the Westlake, Ohio-based enterprise content service provider. Hyland Software. He specifies that the move to the cloud does not prevent the continued use of these applications. There are scenarios in which companies can choose to keep their legacy on-premises technology, including if those companies have many highly customized installations that would need to be re-implemented or ported to the cloud, presenting a myriad of challenges for the customer.

In addition, if a company wishes to have specific administration or access capabilities, these can also lead to staying with on-site solutions; in the cloud, companies would be linked by parameters to the hosted offer.

If a company has decided to move to the cloud but is still tied to existing contracts, they should express their desire to move from on-premises to the cloud to their ECM provider; this vendor likely has a program or options to rewrite their current contract to enable cloud-hosted solutions.

“For the vendor, meeting the needs of their customers – in this case moving to the cloud – is their top priority, and cloud-based solutions also allow an ECM vendor to ease the operational and administrative burden on their customers.” , did he declare.

When migrating from on-premises technology to cloud-based technology, businesses should actively participate in the process and partner with their vendor to ensure the smoothest transitions possible. Vendors will seek to identify any endpoints and third-party integrations that may be affected by the migration, and customers can facilitate this process by directing their vendor to all the processes and systems that are part of their business.

He added that there are significant risks if migrations are not executed correctly, but involving customers in the process can help achieve the best possible outcome.

If a business is in the initial stages of identifying a cloud provider, it should assess not only the provider’s platform and whether it meets their specific business needs, but also these key factors:

  • Supplier’s security history, including any breaches
  • The vendor’s ability to serve my applications from multiple locations, for example in a disaster recovery setting
  • Supplier auditing standards – what national and international standards they adhere to to ensure the level of performance you would get from your supplier.

The cloud as a state of mind

The cloud, however, is a mindset, not a place, Ugur Tigli, CTO in Palo Alto, Calif. MinIO, added. Cloud refers to RESTful APIs (AWS S3 to be precise), transparent scale, containerization and orchestration (Kubernetes), object storage and automation.

“If you adhere to the principles of the cloud, physical location becomes irrelevant. AWS, GCP, Azure, private cloud, Kubernetes distributions (RedHat OpenShift, VMware Tanzu), edge clouds they are all at stake. Choices are made based on performance, control and economy, ”a he declared.

Under these circumstances, how do you manage the move to a cloud-native content management system when existing technology and contracts are involved? The answer is to start with the storage component. Object storage is the primary cloud storage and as such is supported by most vendors on Forrester’s Wave.

The key to an enterprise cloud journey is to disaggregate the compute / application layer from the storage layer. In the context of the question. Its response is to ensure that technologies store their documents, files, videos and images on object storage. The app starts the bridge by selecting cloud native storage.

This provides the option that the business needs in the future. With an S3-compatible object store, the company can migrate the application layer to the cloud (public, private, hybrid) or swap it entirely. The impact is minimized because the “thing” that counts is already on the “cloud” that the application that interfaces with it will catch up.

“Companies that have purchased content management systems need only follow this example: it offers the ‘tomorrow’ option they want with the performance they demand today,” he said. he declares. “They can keep their contracts until they expire or their vendor provides a cloud-native front-end to couple with the back-end. “


Please enter your comment!
Please enter your name here