41–50 of 189 posts
Has anyone struggled to run their own feature flagging service? After root causing slow app starts to be caused by the equivalent offering from Firebase, I've been cautious to use any off the shelf solutions
It's literally a field in your database. I could never fathom why this needs to be an outsourced service never mind an entire company.
Worth noticing a Vercel equivalent: https://github.com/vercel/flags
That is actually their SDK / provider agnostic library. The better parallel to this new Cloudflare offering is Vercel Flags[1] (confusing I know) [1] https://vercel.com/docs/flags/vercel-flags
- anyone have comments/comparisons about launchdarkly vs posthog vs statsig (is it still alive after openai?) vs _____ vs cloudflare flagship?
like a "beginner/intermediate/advanced" progression of what to look out for/what you will want when it comes to feature flags would be highly helpful for me and many others here
I’m always excited when Cloudflare starts offering things that I had to use other providers for because I know it will be solid. We used Statsig at Function. It started out as 2 of us using it on one product and within 12 months, large amounts of our product copy and rollouts were driven off of it. Statsig has client side evals so you can write rules and rollouts based on internal concepts without Statsig’s servers p…
I’m always excited when Cloudflare starts offering things that I had to use other providers for because I know it will be solid. We used Statsig at Function. It started out as 2 of us using it on one product and within 12 months, large amounts of our product copy and rollouts were driven off of it. Statsig has client side evals so you can write rules and rollouts based on internal concepts without Statsig’s servers p…
you use a 3rd party for feature flags? im not "roll my own" for everything but feature flags have not been an issue to roll
Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Still using AWS for email sending so that will be great when it comes
Never underestimate the power of a zero-network-hop abstraction over f(feature_name, context). And context can be extremely tailored to your niche: specific inventory, from a specific supplier, for a specific user of a specific B2B client of a specific business model subtype, who should or shouldn’t see certain features on that specific inventory at certain times. When you can write your own logic, and just run this…
https://www.stigg.io/blog-posts/entitlements-untangled-the-m...
Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Yep I made the switch a couple of years ago for all of my projects and never looked back. Workers, D1, R2, queues, containers, KV Still using AWS for email sending so that will be great when it comes
Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Yep I made the switch a couple of years ago for all of my projects and never looked back. Workers, D1, R2, queues, containers, KV Still using AWS for email sending so that will be great when it comes