growthbook VS The gist

Why did we choose GrowthBook?

I would not adopt a platform that did not support exclusions. I think you should create a marketing page explaining the ways you are superior to the competition. Right now I would pick https://www.growthbook.io/

Seems that no-one mentioned my favorite feature flagging + A/B testing open source tool: https://www.growthbook.io/

What are the differences to Flagr, GrowthBook or Flagsmith?

Thanks for the link - am I getting it right that this is a Feature Flag system akin https://www.growthbook.io/ and PostHog Flags (also OSS)? At least I got this impression from their landing page.

Launch HN: GrowthBook\ (43 comments)

git clone https://github.com/growthbook/growthbook.git cd growthbook docker-compose up -d

For example, in NodeJS you can spawn new shells to call out to other programs on the computer. I use this in my open source A/B testing platform GrowthBook to call a Python script. Something like this:

I use bullmq with node

BullMQ is a pretty solid choice: https://github.com/taskforcesh/bullmq It's the successor of Bull: https://github.com/OptimalBits/bull

BullMQ

For Node.JS you can use something like BullMQ (https://github.com/taskforcesh/bullmq) and then dispatch jobs to the message queue with your worker handling the jobs. You can read about an example for Bull MQ here (https://deadsimplechat.com/blog/best-nodejs-schedulers/#2-bull)

bullmq seems like an open issue

In order to try and mitigate the OOMs. I read the Background Jobs in Node.JS with Redis blog post and implemented Heroku Data For Redis with ioredis, BullMQ and Throng,

The Node.js libraries BullMQ and Bee Queue are also infrastructure and interface. However, you typically have to use their interface.

How to manage that kind of data fetching independently from several data sources? Do I need Message Queue for that? Maybe build individual microservice for each API-client?

This is the ideal scenario for a redis message queue like BullMQ. You could even process that queue in a stand alone process automatically if needed.

At Woovi we use bull for distributed jobs and messages using Redis. If you are starting a fresh codebase, or moving to event driven approach, we recommend to use bullmq which is a modern version of bull.