<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jiggawatts</author><text>This is because neither AWS nor Azure use referential integrity in any of their &amp;quot;cloud scale&amp;quot; databases. For example, Azure uses some hideous JavaScript-based document DB where things like renames, moves, and deletes are hit &amp;amp; miss at best. A never-ending whack-a-mole of bugs and issues.&lt;p&gt;Remember boys and girls: Being &amp;quot;cloud scale&amp;quot; means data corruption and referential integrity violation!</text><parent_chain><item><author>orf</author><text>Shout out to AWS batch, where if you delete the role assigned to a compute cluster the cluster itself becomes impossible to delete.&lt;p&gt;Found this out after using AWS nuke</text></item></parent_chain></comment><story><title>AWS Nuke – delete all resources associated with AWS account</title><url>https://github.com/rebuy-de/aws-nuke</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Marazan</author><text>Even better if you have your cloud formation with the iam role in the same stack and there is something wrong the the rollback can happen such that the iam role gets deleted standing the compute environment and failing the rollback.</text><parent_chain><item><author>orf</author><text>Shout out to AWS batch, where if you delete the role assigned to a compute cluster the cluster itself becomes impossible to delete.&lt;p&gt;Found this out after using AWS nuke</text></item></parent_chain></comment><story><title>AWS Nuke – delete all resources associated with AWS account</title><url>https://github.com/rebuy-de/aws-nuke</url></story>