Fork me on GitHub
#datahike
<
2023-08-08
>
whilo00:08:18

@pat561 Welcome 🙂 ! Yes, this is the right place, although a replikativ channel would be technically more correct. I wrote the S3 backend, mostly with an eye on making Datahike more portable into cloud environments including AWS lambda, so you are exactly asking the right questions. Note that I am not an AWS or S3 expert, I mostly wanted to cover this ground. Feel free to suggest any changes and open PRs! I left X-ray in there because it was in the holy-lambda based code I took inspiration from and AWS users seem to use it https://github.com/FieryCod/holy-lambda/blob/master/examples/bb/native/aws-interop-v2.example/src/aws_interop_v2/example/core.cljc. I am happy to make it optional or remove it if it is in the way of portability (ideally it should be optional). I have also not been able yet to annotate the S3 code sufficiently to make it compilable to native code, then it would be possible to also provide our CLI tools including the new babashka pod working against S3 backends.

Patrick Brown00:08:52

I'm using Konserve across Redis, S3, and I'm about fixing to have a go at IndexedDB. I can rework the s3 one, I did a tiny thank you style PR on the Redis. It's a bit far down the road on a lot of decisions for me interject. I've got a decent idea that I can rework this line https://github.com/replikativ/konserve-s3/blob/d98bdf5c57e6ef5349e02006c4fdb7b07e2e54b0/src/konserve_s3/core.clj#L43 and get something that is more willing to just take any map. I don't know. I don't really do the open source contributing much. I'm going to just have some opinions send a PR when I can stare at it and no worries if it's not for you.

whilo01:08:58

Feel free to open them and I am happy to improve the code 👍 .