SitePoint Sponsor

User Tag List

Results 1 to 3 of 3

Thread: Thinking of AWS SimpleDB?

  1. #1
    SitePoint Evangelist mrwooster's Avatar
    Join Date
    Jan 2006
    Posts
    518
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Thinking of AWS SimpleDB?

    I am considering using AWS's SimpleDB instead of my current MySQL database.

    My reasons for considering the change are:

    My website is one in which the database is growing very large in size, very quickly.

    Using SimpleDB will allow me to have a flexible and easily expanding database, paying for what I use at the current time.

    Using SimpleDB allows me to have a database which is not part of my hosting provider, making changing hosting providers a more simple process.

    Has anyone had any experience with SimpleDB, is it worth the change, and how does it compare to a locally hosted MySQL db?

    Also, I am slightly confused as to what AWS means by 'machine hours'? It says that the first 25 'machine hours' per month are free.... is a machine hour using the database for 1 hour? In which case you would incur 24 machine hours per day, every day? Or is it a measure of the usage of the database? So you might only use 20 machine hours in a month?

    Ty

  2. #2
    Follow Me On Twitter: @djg gold trophysilver trophybronze trophy Dan Grossman's Avatar
    Join Date
    Aug 2000
    Location
    Philadephia, PA
    Posts
    20,580
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    Amazon SimpleDB measures the machine utilization of each request and charges based on the amount of machine capacity used to complete the particular request (SELECT, GET, PUT, etc.), normalized to the hourly capacity of a circa 2007 1.7 GHz Xeon processor.
    It's an abstraction. If you're not handling any queries at midnight, then you're not paying for any machine hours. If you're handling more than a 1.7GHz processor could handle per hour in the afternoon, you'll be paying more than one machine hour per real hour.

    SimpleDB is not the same kind of relational database you're used to with MySQL. It does not have the same structured data and does not support the same kinds of queries. Your first step should be establishing whether it will even work for your application. If so, expect to rewrite your entire data layer.

    A much simpler transition would be to move your MySQL servers onto Amazon EC2 instances and using Amazon Elastic Block Storage for storage. You can continue using MySQL and have unlimited disk space.
    17-29% of paid ad clicks are fraudulent. Get protected with Improvely, your online marketing dashboard.
    Conversion tracking, click fraud detection, A/B testing and more.

  3. #3
    SitePoint Evangelist mrwooster's Avatar
    Join Date
    Jan 2006
    Posts
    518
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Dan Grossman View Post
    A much simpler transition would be to move your MySQL servers onto Amazon EC2 instances and using Amazon Elastic Block Storage for storage. You can continue using MySQL and have unlimited disk space.
    Wow... such a simple idea... definitely the better option. Thanks for the help.

    Ty

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •