[brookst]

At the very least you have to validate everything that touches redis, which means finding everything that touches redis. Internal tools and docs need to be updated.

And who knows if someone adopted post-fork features?

If this is a production system that supports the core business, hundreds of hours seems pretty reasonable. For a small operation that can afford to YOLO it, sure, it should be pretty easy.

[benwilber0]

But why are they spending any time switching away from Redis at all unless they are a hosting provider offering Redis-as-a-service?

I wasn't aware the license had any negative affect on private internal use.

[twoodfin]

The negative effect is that you have to bring the lawyers back in, and they tend to take an extremely conservative position on what might be litigated as offering “Redis-as-a-service”.

[cortesoft]

Would they? My experience is the lawyers sign off when software is being chosen, but then they aren't consulted again.

After that, it is just updating version numbers. Lawyers don't sign off on version upgrades, why would I bring this to them?

[ukuina]

Many legal departments cannot afford nuance when a newsworthy license change occurs. The kneejerk reaction is to switch away to mitigate any business risk.

[freeAgent]

I doubt having lawyers review your usage is more expensive than spending hundreds of hours of dev time to migrate.

[stackskipton]

Our lawyers looked at SSPL since we do host software for customers and it does use Redis and went "Eh, this is as clear as mud." so Valkey it is!