wappalyzer VS Sidekiq

Wappalyzer is an extension for browsers, as well as an online tool that helps developers, designers and marketers with insights into the technologies that are used on any website. This powerful tool assists in understanding the software stack, frameworks, libraries, CMS and many other technologies applied in building specific sites.

Wappalyzer https://www.wappalyzer.com: This one started as a chrome extension, then grew into a one-person million dollar business, the owner makes money by selling data to business associates.

Wappalyzer is a browser extension that identifies the technologies and frameworks used on a website. It's a valuable tool for competitive analysis and staying up-to-date with web technologies.

I have a copy of it from 11th of July, since I used to contibute.

https://github.com/osbre/wappalyzer

Weird and sad to see this extension go private, it was recieving a lot of contributions on GitHub.

Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq.

I'd say Sidekiq is the top competitor here.

There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.

It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594

That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).

Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.

Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but it’s not suitable for processing critical jobs with a low latency guarantee.

https://github.com/sidekiq/sidekiq/wiki/Reliability

> I'm not sure feature withholding has traditionally worked out well in the developer space.

I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.

I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.