3 ms·
I have a strong sense that you're vastly over-engineering something. The solved problem is called an object store. Just use S3 or Azure Storage or Google Cloud
by manigandham 11y ago
I have a strong sense that you're vastly over-engineering something.
The solved problem is called an object store. Just use S3 or Azure Storage or Google Cloud Storage - they all have options for geo-replication and it'll be just as fast or faster than any database replication you set up, while being far more 9's of availability and reliability.
Storing a tiny bit of text for the filename is trivial and you can use any durable database for that.
- LoSboccacc 11y ago> I have a strong sense that you're vastly over-engineering something. and you're 100% right it wouldn't be interesting otherwise :D (I'm not gonna use this on real work no worries)