Book Image

Amazon SimpleDB Developer Guide

Book Image

Amazon SimpleDB Developer Guide

Overview of this book

SimpleDB is a highly scalable, simple-to-use, and inexpensive database in the cloud from Amazon Web Services. But in order to use SimpleDB, you really have to change your mindset. This isn't a traditional relational database; in fact it's not relational at all. For developers who have experience working with relational databases, this may lead to misconceptions as to how SimpleDB works.This practical book aims to address your preconceptions on how SimpleDB will work for you. You will be quickly led through the differences between relational databases and SimpleDB, and the implications of using SimpleDB. Throughout this book, there is an emphasis on demonstrating key concepts with practical examples for Java, PHP, and Python developers.You will be introduced to this massively scalable schema-less key-value data store: what it is, how it works, and why it is such a game-changer. You will then explore the basic functionality offered by SimpleDB including querying, code samples, and a lot more. This book will help you deploy services outside the Amazon cloud and access them from any web host.You will see how SimpleDB gives you the freedom to focus on application development. As you work through this book you will be able to optimize the performance of your applications using parallel operations, caching with memcache, asynchronous operations, and more.
Table of Contents (16 chapters)
Amazon SimpleDB Developer Guide
Credits
Foreword
About the Authors
About the Reviewers
Preface

Partitioning


SimpleDB is designed to provide a maximum of 100 domains per account and each domain is limited to a maximum domain data size of 10 GB. There is always the possibility that the size limitation of 10 GB will be a limiting factor when your dataset needs to be larger. In such cases, SimpleDB gives you the ability to create multiple domains. This will of course mean that data will need to be partitioned among the multiple domains so that each dataset in a domain is under the 10 GB size limit.

Your dataset might naturally partition along some dimension. For example, let us assume that our songs domain is hitting the limit of 10 GB. We could partition our domain into multiple domains, each dedicated to a specific genre. However, this will add complexity to our application as currently SimpleDB domain queries cannot be made across domains. Any partitioning of the data means that we will need to make select queries for each domain and then aggregate the results in the application layer...