I do think there's room for new tools tho, but by definition, they're on the cutting edge and not especially visible if you're not looking. Things like stream processing are already incredibly useful and only getting better. Machine learning could be in this list too. It might not be a 1000% improvement like caching, but that's part of a maturing industry.
Ask HN: Is there server-side software that we are missing in 2018?
21–30 of 115 posts
Re: Ask HN: Is there server-side software that we are missing in 2018?
#22There is some work we are doing (https://kanister.io) to help with these issues but there are a lot of emerging solutions in this space. Look at CNCF's landscape for some more detail.
Re: Ask HN: Is there server-side software that we are missing in 2018?
#23It feels rather like we have too much software.
Re: Ask HN: Is there server-side software that we are missing in 2018?
#24I want a distributed (not cloud) file system that handles many files and WAN latency (i.e. not HDFS). It might be a cross between Git and BitTorrent. It feels like deb repos, PyPI, NPM, CPAN, CRAN, etc. should be put in there, with the addition of binaries for popular architectures. And probably Docker-like images, although I think if they are not opaque blobs, it would be better for rsync-like differential compressi…
Re: Ask HN: Is there server-side software that we are missing in 2018?
#25Re: Ask HN: Is there server-side software that we are missing in 2018?
#26I want a distributed (not cloud) file system that handles many files and WAN latency (i.e. not HDFS). It might be a cross between Git and BitTorrent. It feels like deb repos, PyPI, NPM, CPAN, CRAN, etc. should be put in there, with the addition of binaries for popular architectures. And probably Docker-like images, although I think if they are not opaque blobs, it would be better for rsync-like differential compressi…
Re: Ask HN: Is there server-side software that we are missing in 2018?
#27I want a distributed (not cloud) file system that handles many files and WAN latency (i.e. not HDFS). It might be a cross between Git and BitTorrent. It feels like deb repos, PyPI, NPM, CPAN, CRAN, etc. should be put in there, with the addition of binaries for popular architectures. And probably Docker-like images, although I think if they are not opaque blobs, it would be better for rsync-like differential compressi…
The reason people use cloud services instead of running these themselves is because the cloud storage fee is usually less than paying someone to run a distributed system.
Re: Ask HN: Is there server-side software that we are missing in 2018?
#28I want a distributed (not cloud) file system that handles many files and WAN latency (i.e. not HDFS). It might be a cross between Git and BitTorrent. It feels like deb repos, PyPI, NPM, CPAN, CRAN, etc. should be put in there, with the addition of binaries for popular architectures. And probably Docker-like images, although I think if they are not opaque blobs, it would be better for rsync-like differential compressi…
IPFS sounds a lot like what you want. Tahoe LAFS plays in this space a bit
The newer distributed file systems I've seen don't like permissions. They like cryptographically-backed capabilities. You have the permission to read the file because you have the ability to decrypt, through the key. (Of course, key management is easy ).
Some user-facing distributed filesystem talks drift into FUSE (or similar) territory. A TahoeLAFS dev talks about how users probably don't actually know what they want: https://plus.google.com/108313527900507320366/posts/ZrgdgLhV... (QUIBBLES: REAL FILESYSTEM VS. STORAGE APP section). This is probably less relevant for a package manager.
The first time I read about BitTorrent based deployment was from Facebook.
Re: Ask HN: Is there server-side software that we are missing in 2018?
#29Static website generators.
We already have jekyll and hugo