How does Limiter compare to experimentation platforms eg. LaunchDarkly?
Although we have feature toggles, Limiter does not support A/B testing or experimentation. Limiter is not positioned for dark launching and is instead focused on delivering an opinionated approach to managing feature entitlements and usage plans. Conversely, LaunchDarkly does not support feature entitlements out of the box.
How does Limiter compare to event tracking tools eg. Heap?
Although we have do basic usage tracking (it's simply a counter on each feature), Limiter is not positioned for full-fledged event tracking as we do not store any event metadata. Instead, Limiter strives to be a simplified tool for managing feature entitlements and supporting usage plans.
How does Limiter compare to subscription management tools eg. Paddle, Stripe and Chargebee?
These tools are mostly concerned with the charging side of things eg. implementing usage based charging, charging for add-ons. They do not care about how you handle the non-price related features in your app.
Is Limiter a rate limiter?
Limiter is not a rate limiter, if you attempt to use it as one, you will be rate limited.
These are the current API rate limits:
Usage, Bind, Increment, Decrement, Set: 120 calls per minute
Yes, the documentation can be found here. Do note that the HTTP API is only available for the default backend.
Why should I use an alternative storage backend?
Using the default backend means there will be an additional round trip to our servers for each flag evaluation. This might be a considerable performance hit for you, depending on your use-case. Using a self-hosted backend results in latency savings of up to 200ms.
Why does Limiter support S3 as an alternative storage backend?
S3 offers industry-leading data availability and scalability with relatively low cost that scales well with usage. S3 also comes with strong read-after-write consistency which makes it extremely capable as a remote state storage. Our SDKs offer direct integration with S3, saving one round-trip and hence increasing flag evaluation performance.
Can I modify the feature matrix json directly if I am on an alternative storage backend?
Yes but only those created through Limiter’s UI will be managed by us.
Do you support other storage backends?
We only support managed storage and S3 at the moment, but rest assured that this is on our roadmap. Examples of backends we plan to extend support for are DynamoDB and Redis. If you have a urgent use-case that needs fulfilling, do contact us at firstname.lastname@example.org.
How do we dogfood Limiter at Limiter?
Limiter is simply one of the many clients (which hopefully includes you!) on the platform. The platform syncs Limiter's feature matrix to an internal database. It also keeps track of your usage of Limiter's features. Dogfooding ensures that all of Limiter's features are battle-tested before they are released.