Azure Architecture Design

Question

I am new to Azure and am a bit confused about the blob repository. I need clients to access via FTP / SFTP to pull out files (XML, CSV, EDI, etc.). The pushed files are read by the .net application and written to the database. As I understand it, we would use the role of a virtual machine to create an FTP / SFTP server, a working role to execute .net code, SQL storage for DB storage and Blob for files.

Am I correct in this assumption, and secondly, the VM role can attach a memory cache for writing and reading files, and can the working role attach to the same memory block for reading and writing files.

Example:

the client moved the xml file to the virtual machine via FTP. VM writes an XML file for storage. The role of the working file reads the file, processes it and writes the contents to db.

I think that's right, or am I missing a boat?

thanks

Answer 1

Given that Azure has many services, you have several options. One important thing to consider when using Azure is that your work roles , which are just Windows Server 2008 without installing IIS, are very flexible, so you can do a lot with them - this includes your own FTP server and the possibility of its placement through virtual machines of a working role. FTP for Azure Blob Storage Bridge (on CodePlex) is an example of this.

Alternatively, you can use the web role (which is the same as the working role, but with IIS support) to do the same - so instead of collapsing your own FTP server, you can use the IIS Visual Guide to Configuring IIS to act as an FTP server in Azure can be found in ITQ. Id recommends doing some extra readings to determine which one is better. Also think about your requirements, as this may affect your approach, i.e. scaling, bandwidth, cost, preferred deployment model, etc.

As for file storage, you can use Blob Storage. If you do not need a relational database on your system, you can completely refuse to use SQL Azure (in this case, the web role solution mentioned above will not make much sense), but again, that comes down to your specific requirements.

The official website The official Windows Azure website is a good source of knowledge, especially if you are starting out, so do not rush to view some of the related documentation.