Talk:Dynamo (storage system)

Computing Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.

Internet Low‑importance

	Internet portal This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InternetWikipedia:WikiProject InternetTemplate:WikiProject InternetInternet articles
Low	This article has been rated as Low-importance on the project's importance scale.

Databases (inactive)

This article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases articles

Catch-22[edit]

"Dynamo is a highly available,[non-primary source needed]..." How is it possible to get a non-primary source on a propriety system whose interfaces are all private? --Blake8086 (talk) 02:37, 29 August 2010 (UTC)[reply]

scale automatically[edit]

"Although the database will not scale automatically, administrators can request more throughput and DynamoDB will spread the data and traffic over a number of servers using solid-state drives, allowing predictable performance"
This request can be done automatically, so how is it not scalable automatically?
https://aws.amazon.com/blogs/aws/auto-scale-dynamodb-with-dynamic-dynamodb/
http://media.amazonwebservices.com/AWS_Storage_Options.pdf - "If you need fully- automated scaling, Amazon DynamoDB may be a better choice."
--Ericpardee (talk) 21:30, 26 April 2016 (UTC)[reply]