CloudM Migrate's architecture and default settings are specifically designed to maximize throughput and maintain a smooth migration, even when facing common platform limitations such as API throttling and rate limiting. It achieves this by intelligently adapting to and navigating these constraints.
Understanding Throttling, Rate Limiting, and API Quotas
Although these terms are often used interchangeably, they refer to distinct platform mechanisms, and CloudM is built to handle all of them.
- Throttling: A platform's reactive measure to slow down a user or application that is making too many requests. It's like a warning that tells you to slow down before you get cut off.
- Rate Limiting: A proactive, hard limit on the number of requests you can make within a specific, short timeframe (e.g., 100 requests per second). When you hit this limit, the platform will block your requests.
- API Quotas: A hard, cumulative limit on the total number of requests you can make over a longer period, such as a day. Once this limit is reached, all further requests are blocked until the quota resets.
Intelligent Architecture
The core of CloudM Migrate's ability to maximize migration speed and reliability lies in its intelligent architecture. We understand that while we cannot control the limitations set by source and destination platforms, we can control how our software responds to them. This architecture is uniquely configured to adapt to the specific behaviors and API rules of each platform.
- Adaptive Throttling: CloudM Migrate is engineered to maximize migration throughput in throttled conditions by using exponential retries. This means when a migration task encounters a rate limit, the software will pause for a brief period, then intelligently retry the task. If it fails again, it will increase the pause time before the next retry. This process ensures that CloudM avoids being blocked and continues to migrate as much data as possible.
- Configurable Levers: CloudM Migrate's settings, which are optimized by default, include configurable "levers" that allow for granular control. While increasing these settings can potentially increase migration speed, it can also increase the risk of encountering rate limiting or throttling. Conversely, if you encounter throttling, decreasing the settings can be used as a key troubleshooting step to reduce load and continue the migration successfully. This allows you to adjust parameters to best suit your environment and specific migration needs.
Visibility into Throttling
CloudM Migrate Throttling Indicators provide you with real-time visibility so you can see when throttling is impacting your migration. On the progress page, you will see clear indicators and status updates that inform you if a source or destination platform is slowing down the migration. This visibility helps you diagnose issues and decide whether to adjust your settings or take a pause.
Related Information
For a deeper understanding of factors that affect migration speed and how CloudM Migrate handles specific platform limitations, please review the following articles: