Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The race to replace Redis

lwn.net

Post reply on HN
Print view View original

431–440 of 520 posts

Re: The race to replace Redis

#431

Post by lolinder »

sa-code wrote: post #184
ayakang31415 wrote: post #124

There is an easy solution not just for this, but for other potential masses: Just go with MIT license and make money with support

How does this stop you from "getting Jeff'd", i.e. when AWS takes your own source code and competes with you?

"Getting Jeff'd" is only an existential crisis if your goal is to own the majority of the pie. Postgres's contributors come from a bunch of different companies who all manage to make enough money off of Postgres to pay them [0]. That is the only financial metric that really matters for funding a FOSS project.

The problem with these companies is that they actually were trying to make large returns for shareholders rather than simply earn enough to keep paying the developers.

[0] https://www.postgresql.org/community/contributors/

Re: The race to replace Redis

#432

Post by wokwokwok »

BoorishBears wrote: post #362
wokwokwok wrote: post #333

Earlier quoted context omitted.

> Just use this pre-V1 public beta software I stumbled upon instead. …but I mean, I’m not really up for playing the “pedantically correct about what he/she said” game with you. Instead how about you comment on the point I’m actually making, which is: opensearch is perfectly fine for most people. For most people, there is no meaningful distinction between elastic and opensearch. Opensearch is a healthy project which r…

No one's asking you to play any games: I'll settle for reading before you comment. > Also you can just keep your data in postgres and use paradedb and stop having to deal with dramatically more expensive infrastructure and the JVM. That was the comment I replied to. If you thought OpenSource was pre-V1 public beta software I'm not sure why you're even opining on this.

> If you have any meaningful or compelling argument why any of those three things is not true by all means, I’d love to hear about it.

Re: The race to replace Redis

#433

Post by Timber-6539 »

packetlost wrote: post #417
Timber-6539 wrote: post #412

Earlier quoted context omitted.

Sometimes I get the feeling all the folks touting podman as a drop-in replacement for docker are doing it in bad faith. Every few years I try to replace my containers managed through docker-compose and it's always a sure miss. Before podman gained official support for the docker-compose spec, there was an unofficial podman-compose project that sort of worked save for a few podman incompatibility bugs here and there.…

> Noped out when I tried to create a VPN with a podman container and it was failing requiring me to enable a kernel module (TAP or TUN can't remember exact error) to create a vpn. Those are pretty standard kernel modules for enabling userspace networking, which if you were using podman in rootless mode you need (along with another userspace networking package, slirp4netns). "Drop in replacement" does not mean there's…

Podman doesn't expose an interface for enabling kernel modules. The error message is intentionally intended to discourage users from doing administration on systems, just like the other similar messages you'll get about trying to use "privileged" ports (Am sure you can get over the kernel module tun creation and other limitations by using something like --privileged but at that point, why not just use docker if you are going to run containers "insecurely".

And for the sake of this argument, drop-in replacement means I can take my tools and move them over to the alternative with little to no extra work needed on my part.

Re: The race to replace Redis

#434

Post by bawolff »

llm_trw wrote: post #149
bawolff wrote: post #104

Earlier quoted context omitted.

This is not a new idea... i mean its so old it was called out as being "not free" back in the 80s by the gnu project.

The GNU project has failed at getting source code to users so badly that despite owning a half dozen GPL based devises I have no access to the source code of any of them. At this point listening to them is at best pointless and at worst actively harmful. This is what happens when the last time you worked at a real job was some time in the 1980s.

Have you tried? Did you write a letter to the vendor asking fot source code? Did they refuse?

Re: The race to replace Redis

#435

Post by maerF0x0 »

brody_hamer wrote: post #48

It wasn’t clear to me until I read their blog, that redis will remain free to use in their “community edition”, which will continue to be supported and maintained (and improved!) So we as developers don’t have to scramble to replace redis in our SAAS apps and web based software. This is more about preventing AWS from eating their lunch by providing redis-as-a-service, without paying any sort of compensation to the re…

Would be nice if Redis wasnt eating Lua's lunch and would make a big (public) donation to https://www.lua.org/donations.html#donation (Maybe they do, but it wasn't something i could find evidence of)

Re: The race to replace Redis

#436

Post by maerF0x0 »

rs_rs_rs_rs_rs wrote: post #176
punnerud wrote: post #166

Interesting that around 40% of the commits to Reddit is from Chinese companies (Tencent 24.8%, Alibaba 6.8, Huawei 5.2, Bytedance 2)

Why is that interesting?

Because tencent consistently won Pwn2own and other CTF competitions until their government turned protectionist/isolationist and disallowed them from disclosing 0days to the world?

https://cyberscoop.com/pwn2own-chinese-researchers-360-techn...

Re: The race to replace Redis

#437

Post by evanelias »

rad_gruchalski wrote: post #370
mythz wrote: post #320

Earlier quoted context omitted.

hence the relicensing

It’s hard to argue that a use permitted by the original license is „predatory”.

That's fair in isolation, but one can justifiably argue that a repeated pattern of behavior is clearly predatory.

Specifically: have the major cloud providers ever created a successful FOSS database, cache, or fulltext search index project from the ground up? By this I mean, a FOSS project with its own protocol, own community from scratch, not a fork or a re-implementation or based on another FOSS project, nor a late-stage company acquisition.

I'm struggling to think of even a single example. Even for broader infrastructure (not just db/cache/search), there's few examples, only Kubernetes comes to mind rapidly.

If the cloud providers are widely practicing "FOSS for thee but not for me" with respect to creation of new infrastructure projects, that's predatory and unsustainable.

Re: The race to replace Redis

#439

Post by busterarm »

BoorishBears wrote: post #151
busterarm wrote: post #118

Earlier quoted context omitted.

Teams should refuse to look at Elasticsearch. It's license is SSPL and they ship free and non-free features in the same binary. It's a ticking time bomb to run it in your company. Also you can just keep your data in postgres and use paradedb and stop having to deal with dramatically more expensive infrastructure and the JVM.

Ah yes, battle-tested Elasticsearch is a ticking time bomb for not wanting to get their lunch eaten by Jeff Bezos. Just use this pre-V1 public beta software I stumbled upon instead.

paradedb is mainly just a package of established/battle-tested postgres extensions like bm25 and pgsparse all on top of cloudnative-pg.

Re: The race to replace Redis

#440

Post by dralley »

Timber-6539 wrote: post #433
packetlost wrote: post #417

Earlier quoted context omitted.

> Noped out when I tried to create a VPN with a podman container and it was failing requiring me to enable a kernel module (TAP or TUN can't remember exact error) to create a vpn. Those are pretty standard kernel modules for enabling userspace networking, which if you were using podman in rootless mode you need (along with another userspace networking package, slirp4netns). "Drop in replacement" does not mean there's…

Podman doesn't expose an interface for enabling kernel modules. The error message is intentionally intended to discourage users from doing administration on systems, just like the other similar messages you'll get about trying to use "privileged" ports ( Am sure you can get over the kernel module tun creation and other limitations by using something like --privileged but at that point, why not just use docker if you…

>Am sure you can get over the kernel module tun creation and other limitations by using something like --privileged but at that point, why not just use docker if you are going to run containers "insecurely".

Because at least you can tell that it's insecure, rather than insecurity being the default?

Post reply on HN