Apr 6, 2015
Loading...
seen from United States
seen from China
seen from Bahrain
seen from United States
seen from Mexico
seen from India
seen from China
seen from Australia
seen from Philippines
seen from United States
seen from United States
seen from Italy
seen from United States
seen from Italy
seen from United Kingdom
seen from Italy
seen from Malaysia
seen from Italy
seen from Malaysia
seen from Italy
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
A Developer's Guide to Amazon SimpleDB (Developer's Library)
A Developer's Guide to Amazon SimpleDB (Developer's Library)
Rating: List Price: Discount: 0.00 Sale Price: (as of 12/31/1969 16:00 PST)Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply to the purchase of this product.. Check Price Right Now! Availability: Free Shipping: unspecified
Product Description
Details
No features available.
New Post has been published on http://cloudifica.com/a-developers-guide-to-amazon-simpledb-developers-library/
#cloudstorage
Sdbport exports & imports data from AWS SimpleDB domains. It can be used as a [ruby] class or stand alone CLI.
intuit/sdbport This does not work with IAM privileges granted to the CLI... HOWEVER boto comes with a command sdbadmin that can back up an amazon simpleDB to XML.
Uses for Amazon SimpleDB: authentication
Immediately after Amazon SimpleDB was announced, I started to conjure up possible uses for the service. Clearly there are limitations on the amount of data you can store, and you don't have anywhere near as many handy functions and capabilities as you do with MySQL, for example. Still, for a simple application where you'd like to avoid scaling issues, SimpleDB might be the answer. I'm thinking of an application with relatively small amounts of data per entity, such as Twitter, which only stores 140 character strings of text. Obviously you may not be able to store entire 1,000 word blog posts with SimpleDB, but other aspects of your site/application may be an ideal fit. Amazon even says so themselves:
Amazon SimpleDB is designed to store relatively small amounts of data and is optimized for fast data access and flexibility in how that data is expressed.
In combination with Amazon S3, you could use SimpleDB to store file pointers, while maintaining the actual large files on S3 - completely minimizing your costs to transfer/regulate the application.
In order to minimize your costs across AWS services, large objects or files should be stored in Amazon S3, while the pointers and the meta-data associated with those files can be stored in Amazon SimpleDB. This will allow you to quickly search for and access your files, while minimizing overall storage costs.
Pretty soon all aspects of hosting a web site will be managed and scaled effectively through services such as S3 and SimpleDB. What are we paying third-party hosting companies for?
Use SimpleDB for user details
If you're application requires authentication, why not use SimpleDB to store usernames and passwords? Heck, you could even store all user details. This would reduce the load on your own database server, for this frequently accessed portion of your application. Everyone has to log in, right? How many requests are for users logging in, ie: verifying the password, etc? Probably tons. This is the entrance into your app. Even the API must verify the credentials. Push this realm onto SimpleDB and only query for the actual content on your own database server. This is just one example of using SimpleDB.
Amazon SimpleDB vs. Google BigTable
It seems Google is poised to announce a service similar to Amazon SimpleDB - Google BigTable. BigTable would allow developers to utilize the powerful infrastructure of Google's global network to provide efficient and scalable database access. The key feature making it better than SimpleDB? BigTable could be free to use. I'll have to be honest - I haven't used SimpleDB yet. I know it has restrictions on data length, and it requires learning new syntax. If Google can soften some of the restrictions and learning curve, I think they could have very impressive product. Google's products are typically user-friendly, whereas Amazon's web services are just the bare-bones service. How you interact with it is up to you - specifically, your technical skill level. This means there are usually no intuitive user interfaces for interacting with Amazon's web services. I can see Google making BigTable much more user-friendly, and possibly incorporating it into Google Apps, for example. And if it's free, goodnight SimpleDB.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
SimpleDB::Client 1.0600
I've released SimpleDB::Client 1.0600 to CPAN. SimpleDB::Client is used to connect to Amazon SimpleDB. The only new thing in this release is a command line app called "simpledb" contributed by Andrew Solomon.Â
Amazon SimpleDB export
Over at Pistachio HQ we're a big fan of Amazon Web Services, and we've been using SimpleDB since day 1. However, for one reason or another we've needed to export our data and it turns out there's no tools that do that... until now!
It does exactly what we want it to.. get our data. If you need to export your data, check it out. It's open source and hosted over on Google code:Â
http://code.google.com/p/pistachiomedia-simpledb-export/
When you get your data, why not say thank you to Gary on Twitter, he developed it :)
Prasanna Padmanabhan and Shashi Madapp posted an article on the Netflix blog describing the process used to migrate data from Amazon SimpleDB to Cassandra:
There will come a time in the life of most systems serving data, when there is a need to migrate data to a more reliable, scalable and high performance data store while maintaining or improving data consistency, latency and efficiency. This document explains the data migration technique we used at Netflix to migrate the user’s queue data between two different distributed NoSQL storage systems.
The steps involved are what you’d expect for a large data set migration:
forklift
incremental replication
consistency checking
shadow writes
shadow writes and shadow reads for validation
end of life of the original data store (SimpleDB)
If you think of it, this is how a distributed, eventually consistent storage works (at least in big lines) when replicating data across the cluster. The main difference is that inside a storage engine you deal with a homogeneous system with a single set of constraints, while data migration has to deal with heterogenous systems most often characterized by different limitations and behavior.
In 2009, Netflix performed a similar massive data migration operation. At that time it involved moving data from its own hosted Oracle and MySQL databases to SimpleDB. The challenges of operating this hybrid solution were described in a the paper Netflix’s Transition to High-Availability Storage Systems authored by Sid Anand.
Sid Anand is now working at LinkedIn where they use Databus for low latency data transfer. But Databus’s approach is very similar.
Original title and link: From SimpleDB to Cassandra: Data Migration for a High Volume Web Application at Netflix (NoSQL database©myNoSQL)