Jasper Siepkes

@pnarayanan I just noticed #587. Seems like a good and well thought out approach!

@pnarayanan Regarding uniqueness of names within a container namespace; I stumbled across an AWS FAQ ( https://aws.amazon.com/s3/faqs/ ) where they describe the consistency model for S3 buckets (containers) as: >...

@pnarayanan I had a thought regarding what to do when a user stores multiple blobs with the same user given name (concurrently). In S3 you can enable keeping track of...

@pnarayanan I read the document, good read! I think what I outlined above fixes 3 things which the document identifies as issues that still need to be solved: * Key...

@pnarayanan I'm currently inventorying what would be required to implement this (I might want to take a shot at this). From what I understand is that you are proposing is...

Small update; I did some thinking about using a K/V store as a naming backend (For example using [LinkedIn's Voldemort](http://www.project-voldemort.com/voldemort/) or Kafka Streams backed by RocksDB). However while blob names...

@yhilem Getting the Ambry frontend to expose an S3 compatible (HTTP) API is probably the easy part. The hard(er) part is coming up with the design on how to implement...

@antcs I think even the CoreOS authors may have gotten it wrong. As stated in #7191 even if you can make an atomic snapshot of the backend Vault itself doesn't...

@thiloplanz Yeah that thought occurred to me too. I'm no expert on Vault's low level storage so what follows is mostly my deduction and assumptions so I could be wrong....

@chrishoffman I don't want to be pushy or sound alarmist (I realize you don't owe me anything) but I'm somewhat unsettled by the fact that currently I don't really see...