CODEWITHSUNDEEP
sqldatabaseazure
wirate
wirate

Reputation: 695

Scalable CRUD application. Storage technique

We are talking about a CRUD application with a little background processing (about 20 decisions per user per day. Not big). We are planning for about 20 million transactions a day. Most of these transactions will be small textual. About 15% will be images sized at about 1MB. Mostly READ. Number of clients could be like 500,000 to 1 million.

We are thinking of hosting it on Windows Azure. For this kind of application, what storage techniques could I use? I was thinking about Azure Tables for images, SQL Azure for other transactional data. Would making more than one database make it more scalable? I mean, if I have two entities, I could make two databases hosted on two different independent servers breaking normalization. Would that be beneficial? I am confused here don't know much about handling large data.

Upvotes: 2

Views: 277

Answers (2)

viperguynaz
viperguynaz

Reputation: 12174

Start by reading Windows Azure Storage Abstractions and their Scalability Targets. You can't really store images in Azure Tables. They are limited to 1MB per entity. You could store the images in Azure BLOB (with CDN) enabled for efficient delivery and instead of SQL, store your property data and links to the images in Azure Tables. The referenced article describes scalability and performance targets.

Upvotes: 3

NavaRajan
NavaRajan

Reputation: 1860

If you are storing the image in Binary format then azure table wont be adequate because max size of a table row is 1MB (including partition key and row key).So for storing images Blob storage is best....

If the transactional data is nonRelational then you can use Azure Table... Which can scale very well than sql azure. http://msdn.microsoft.com/en-us/library/windowsazure/jj553018.aspx

Upvotes: 0

Related Questions