110 likes | 116 Views
Whether it is data conversion or data migration, ISVs are fast learning the ropes when it concerns time and cost savings. Even then, there are few points that ISVs need to take into account when the customers are moving to cloud leading to data migration to cloud.
E N D
Before ISVs Migrate to Cloud Whether it is data conversion or data migration, ISVs are fast learning the ropes when it concerns time and cost savings. Even then, there are few points that ISVs need to take into account when the customers are moving to cloud leading to data migration to cloud. Here’s a quick low-down:
Where to store? Before migration, ISVs need to select from the various options offered by Cloud Vendors regarding data storage. For instance, S3 is perfect for outsized media filed whereas RDS is the best option for web apps. One can even go for Simple DB if the data is query-able lightweight. When the storage is right, data migration becomes far easier.
Where to locate? Data location becomes tough if the cloud vendor doesn’t give the facility to locate the data. Before choosing a cloud vendor, it’s better to check if they allow you to identify the target storage and path. The trouble can multiply if customers are firm on the facility of data location, and not providing for the same can result in the loss of customer.
How to select data? “What to keep and what to migrate” is the major decision when migrating data to the cloud. A particular data might be of use on premise for ‘n’ number of reasons. For this particular complexity, tools need to be devised that segregate the data based on various attributes. Thereafter, these tools can extract the data that need to be migrated.
What about shared schema model tenant? When it is shared schema model tenant, then the already used ETL tools will not assist it. ISVs will have to keep themselves ready with the solutions much before they move to shared schema multi tenant.
Which are the data loading strategies? ISVs need to develop APIs much before to save troubles afterwards. They can choose from numerous options. Simple APIs inspect data model failures or non- compliance but there might be a need of tenant specific model extension in case of multi tenant cloud. Workflow based APIs run predestined workflows and come up with pre- defined errors in case of deviations
How to verify migration? Clouds do not support standard top down, bottom up equivalence or bottom up fingerprint verification approach. This makes way for custom methods that need to be developed ahead of time. To Know More >> CLICK HERE
Leo TechnoSoft Snapshot Overview - Global partner product development provider with delivery centers in Los Angeles, Chicago and India (Offshore). - Specializes in Cloud, SaaS and Enterprise Product Engineering for Startups, Entrepreneurs, ISV(SME). Value offering Industries Technology Healthcare/Life Sciences Finance Retail Manufacturing Real Estate Partnered Product Development Technical, Operation and Sales Management Expertise SaaS & Cloud solutions Customer Relationship Management Sales and Marketing VC Connections and relationships www.leotechnosoft.net 11
OUR PRESENCE Adequate infrastructure to scale up at the drop of a hat Backend Data Center / Infrastructure set up Global Offices to support 24x7 Client Operations For more information email us at enquiry@leosys.net. www.leotechnosoft.net
THANK YOU 13