6 responses to Scaling an FTP Ingestion Service Using #Azure Traffic Manager

  1. 

    Hi there. Really great post! I find that there’s lots of information on geo replicating web apps, VMs etc. but very little on Azure storage, SQL etc.

    Given that the file uploaded via FTP still has to make the trip to the central storage account, did you find much improvement in speed compared to just uploading directly to storage from the various traffic-managed VMs? My feeling is that this would be a costly solution (even for small VMs) and that there world not be much of a speed improvement in getting the file to its final destination.

    Like

    • 

      Hi, great question. The post was written with the FTP protocol in mind. I absolutely agree that working directly with Azure storage is best for reasonably sized documents. If we are talking about volumes of data, then it may be time to look at more specialized services and solutions. Working with this FTP scenario, having an FTP server close to the uploader was key because of delays. The secondary data movement was not as important in terms of speed. Bringing data into Azure was the key to success even if the primary storage account was inaccessible. Managing application level replication is also possible where data could be replicated in each region instead of having a central copy. Cost is definitely something o have on the radar and will impact your final architectural choices.

      Like

  2. 

    Also, what kind of criteria have you set for scaling?

    Like

    • 

      At the time of writing this post, I had not done any work around scalability. I was mostly relying on the fact that I had instances in multiple geolocations. This would definitely be something to explore in the future.

      Like

  3. 

    Given that the file uploaded via FTP still has to make the trip to the central storage account, did you find much improvement in speed compared to just uploading directly to storage from the various traffic-managed VMs? My feeling is that this would be a costly solution (even for small VMs) and that there world not be much of a speed improvement in getting the file to its final destination.

    Like

Trackbacks and Pingbacks:

  1. Dew Drop – March 11, 2015 (#1972) | Morning Dew - March 11, 2015

    […] Scaling an FTP Ingestion Service Using #Azure Traffic Manager (Alexandre Brisebois) […]

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s