for storing strings larger than 4k in datomic cloud, there's a number of ways to get that wrong, I suppose..? 🙂

would this work? Generate a squuid, store the string in external storage along with that squuid, wait for external storage to report A-OK, store that squuid in datomic?

I was thinking of using the hash of the string as the filename

Watch out for filename collision when two strings happen to be equal

sounds better to create an unique ID every time you want to create a fact for that string, if you override the old one, and the transaction fails, then external storage and datomic is out of sync

and that 🙂

I mean, if two strings are equal - then no need to store it again? 😄

there’s the chance of hash collisions but it should be fairly low

Yeah that’s true...external storage would need immutable/accrete-only semantics then yeah? Every modification creates a new, for example, S3 object.

yep exactly

otherwise you couldn’t use historical queries to read past strings

Right. I need an app that shocks me every time I revert back to mutable place oriented thinking.

😂

well, I’m working on a blog-esque type app right now so these problems are at the forefront of my mind

@augustl I think this would prevent the out of sync issue you mentioned

yeah, seems like it would

only downside I can think of is to have to create hashes for potentially large strings 🙂

but for something like a blog that probably shouldn't be a problem

anyone setup an Ion as a custom authorizer for API Gateway?