I’ve utilized this in Lambda@Edge for use case half feature flag-y, half HTTP routing/proxy serving rules as mentioned in a sibling comment. Lambdas pick up ~50-200MB of data on first boot, and keep their copy through their lifecycle.
As requests come in, gather their features, convert to effectively an int vector, filter for row where match and serve request
As requests come in, gather their features, convert to effectively an int vector, filter for row where match and serve request