I’ve completely switched away from using Minio (and just the S3 protocol in general) in all of my projects.
I’ve found that the WebDAV protocol is better for object storage in almost every case. It’s also way simpler to use and understand.
Now it’s time for me to shill:
I wrote my own WebDAV server called Nephele. It’s free and open source, and you can run it on Docker. Probably doesn’t help if you’re using something that requires S3, but if you’re building something, I implore you to migrate away from S3.
It’s simpler, there is a client for everything even mobile phones, it has a move command, it has props that can be edited without a copy command, pagination is however you set it up to be rather than a one size fits all approach, it can be just as scalable as S3 if you build it to be, it has much simpler locks that make them easier to use so you might actually use them, keys can be longer than 1024 characters, actual directories exist.
That’s just the protocol level. The biggest benefit for me isn’t really at the protocol level, but part of the design of my own WebDAV server: deduplication. I can throw the same file into my server with 50 different keys, and it will only take up the space of one copy on disk. This basically moved the logic of deduplication from my application to the blob store. Mountains easier from an application design perspective.
There are use cases where S3 is better, but they are few and far between. And, WebDAV is extensible. You can build whatever functionality you need into it, rather than using some proprietary protocol.
MacOS hates webdav (And I do hate my Mac too !) And their implementation is outdated… Maybe I didn’t find the right configuration to make is work properly like samba shares (after some special/specific mac configuration on the samba server side it works like a charm !!) but whenever a file got updates in an automated way, it somehow goes poof and vanished from my server… Scary shit !
I’ve completely switched away from using Minio (and just the S3 protocol in general) in all of my projects.
I’ve found that the WebDAV protocol is better for object storage in almost every case. It’s also way simpler to use and understand.
Now it’s time for me to shill:
I wrote my own WebDAV server called Nephele. It’s free and open source, and you can run it on Docker. Probably doesn’t help if you’re using something that requires S3, but if you’re building something, I implore you to migrate away from S3.
Why is WebDAV better?
It’s simpler, there is a client for everything even mobile phones, it has a move command, it has props that can be edited without a copy command, pagination is however you set it up to be rather than a one size fits all approach, it can be just as scalable as S3 if you build it to be, it has much simpler locks that make them easier to use so you might actually use them, keys can be longer than 1024 characters, actual directories exist.
That’s just the protocol level. The biggest benefit for me isn’t really at the protocol level, but part of the design of my own WebDAV server: deduplication. I can throw the same file into my server with 50 different keys, and it will only take up the space of one copy on disk. This basically moved the logic of deduplication from my application to the blob store. Mountains easier from an application design perspective.
There are use cases where S3 is better, but they are few and far between. And, WebDAV is extensible. You can build whatever functionality you need into it, rather than using some proprietary protocol.
Thanks!
MacOS hates webdav (And I do hate my Mac too !) And their implementation is outdated… Maybe I didn’t find the right configuration to make is work properly like samba shares (after some special/specific mac configuration on the samba server side it works like a charm !!) but whenever a file got updates in an automated way, it somehow goes poof and vanished from my server… Scary shit !
Yeah WebDAV is significantly better for our use cases, S3 has so many weird limitations and it’s hard to find clients for it.