title: Managing dev/staging/production on DynamoDB - Conflicting Approaches. Does using DynamoDB Mapper for use of one approach?
body: <p>This question was asked 2 years here: <a href="https://stackoverflow.com/questions/9877136/managing-dev-staging-production-on-dynamodb?rq=1">Managing dev/staging/production on DynamoDB?</a>
  also here: <a href="https://stackoverflow.com/questions/17372601/dynamodb-staging-production-development-versions">DynamoDB Staging/Production/Development versions</a></p>
  
  <p>The accepted answer was creating separate accounts, with consolidated billing.  There seems to be conflicted approaches.
  For instance Peter Sankauskas in his comments suggested that is not the "standard way" anymore.  </p>
  
  <p>His suggestion was to use:
  "Use tags and naming conventions to separate staging and production."</p>
  
  <p>Does his solution still hold up when using the Java SDK DynamoDBMapper as the table names are implanted in the annotations?</p>
  
  <p>Thanks.
  (PS: I would have added a comment, but I don't have the reputation.)</p>