yadda yadda yadda

When and who should emit which event.

As it was present before, and maybe useful for snowplow integration.

So we can also have a way of `apt-get install metarank` way of installation. Although it's not high-prio.

Mentioning feature store and all the point-in-time joins happening.

Migrate to a hand-written decoders for payloads with `deriveConfiguredCodec`. Generic-extras is a single giant scala2-only macro which will probably never be migrated to scala3.

As it seems to be not maintained anymore, and has no scala3 build.

Metarank 0.5.x uses redis a lot: * it does a couple of round-trip requests for each event, which may result in a very low import throughput * how low is...

When you embed everything into a single container

Imagine a use case when you only use Metarank in static ranking mode - so all the users will always get the same ranking: * then in practice you don't...

The code: https://github.com/metarank/metarank/blob/master/src/main/scala/ai/metarank/config/Config.scala#L35C1-L35C68 The doc: https://docs.metarank.ai/reference/overview/data-sources#apache-kafka