Cloudwick Collaborates with Pepperdata on AWS Migration Service

By Ken Briodagh March 29, 2019

In a recent release, Pepperdata, a big data Application Performance Management (APM (News - Alert)) company, and Cloudwick, provider of digital business services and solutions, announced a collaborative offering for enterprises migrating their big data to Amazon Web Services (News - Alert) (AWS). Pepperdata reportedly provides Cloudwick with a baseline of on-premises performance, maps workloads to optimal static and on-demand instances, diagnoses issues that arise during migration, and assesses performance after the move to ensure the same or better performance and SLAs.

“The biggest challenge for enterprises migrating big data to the cloud is ensuring SLAs are maintained without having to devote resources to entirely re-engineer applications,” said Ash Munshi, Pepperdata CEO. “Cloudwick and Pepperdata ensure workloads are migrated successfully by analyzing and establishing a metrics-based performance baseline.”

For Cloudwick's AWS Migration Services, Pepperdata is installed on customers' existing, on-premises clusters — it takes under 30 minutes — and automatically collects over 350 real-time operational metrics from applications and infrastructure resources, including CPU, RAM (News - Alert), disk I/O, and network usage metrics on every job, task, user, host, workflow, and queue. These metrics reportedly are used to analyze performance and SLAs, accurately map workloads to appropriate AWS instances, and provide cost projections. Once the AWS migration is complete, the same operational metrics from the cloud are collected and analyzed to assess performance results and validate migration success.

“Migrating to the cloud without looking at the performance data first is risky for organizations and if a migration is not done right, the complaints from lines of business are unavoidable,” said Mark Schreiber, General Manager, Cloudwick. “Without Pepperdata's metrics and analysis before and after the migration, there is no way to prove performance levels are maintained in the cloud.”




Edited by Ken Briodagh


Original Page