• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 656
  • Last Modified:

EC2 Vs NAS Or SAN Storage For High Transaction Read and Write Web Apps using MySQL

Greetings,

What's the best performance concept for an enterprise environment with lots of reads and writes. Would we benefit from EC2 concept or NAS\SAN concept? The MySQL environment has bottle neck issues and we want to make sure we are using the most ideal concept to compliment or web apps and MySQL database environment. Please chime in.
0
Omega002
Asked:
Omega002
1 Solution
 
oztrodamusCommented:
I would be afraid of any cloud provider that could not contractually guarantee they aren't going to farm out their storage to some other provider that you can't see, because it's in the cloud. For that reason if high transaction rates are what you require I would stick with a SAN. If cost control is what you're after todays iSCSI can be just as good as FC.
0
 
shalomcCTOCommented:
When you say EC2, do you mean the non-relational Amazon SimpleDB, or something else?

There is a growing tendency among really high volume transaction producers to use "non standard" databases, like Cassandra, Dynamo and others. It eventually depends on your application design whether you can use such a solution.


0
 
lynxITCommented:
I would suggest the best question to ask first is what security needs (i.e does it need be kept private?) surround the data?  

If its high security (ie personal data that your company or organisation is responsible for) that has strict usage guidelines then an in-house NAS/SAN would (in my opinion) be your only option.  If the data does not need to be kept that secure, the EC2/S3 and a NAS/SAN could both be options.

Is this purely data in a database, or is this data to both database and disc?
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
AncillasCommented:
Is the bottle neck the connection to the DB server or is disk activity causing a long write queue?  If it's a long write-queue, you can scale upwards and get a bigger machine to handle the DB.  In this case, Amazon EC2 would be a fine solution.

If the network is your bottle-neck, you'd be better served using a SAN solution.

Going back to EC2, you might want to do a quick google search to see if there are any issues with their EBS volumes and read/write intensive applications.  We used to experience write queue issues with our app, but a recent patch at Amazon fixed the issue.
0
 
Omega002Author Commented:
None
0
 
Omega002Author Commented:
none
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now