Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Flagship

developers.cloudflare.com

Post reply on HN
Print view View original

31–40 of 189 posts

Re: Cloudflare Flagship

#31

Post by jasonjmcghee »

OptionOfT wrote: post #23
crabmusket wrote: post #22

Looking at the docs for their JS SDK, they have this warning: > The client provider requires an API token to fetch flag values. This token is not scoped to a single app, so anyone with the token can evaluate flags across all apps in your account. Use the client provider with caution in public-facing applications. https://developers.cloudflare.com/flagship/sdk/client-provid... Can anyone clarify... why the client SDK,…

Let's think about it. This is probably something used internally at CloudFlare and someone thought I'd be interesting to make it public. There is no way 6 months ago someone at CloudFlare thought it was a good idea to build a competitor to say LaunchDarkly.

Hmm not sure I necessarily agree. Cloudflare's strategy has been looking like "the only platform you need" for a while now.

Their recent features / announcements have been equivalent to:

(LaunchDarkly)

Resend, Firecrawl, CrewAI, Helicone, Replicate, Pinecone

-

Which like… many companies have a painful procurement process. If all you need is Cloudflare, and prices are within reason- why not use them

Re: Cloudflare Flagship

#33

Post by bg24 »

OptionOfT wrote: post #23
crabmusket wrote: post #22

Looking at the docs for their JS SDK, they have this warning: > The client provider requires an API token to fetch flag values. This token is not scoped to a single app, so anyone with the token can evaluate flags across all apps in your account. Use the client provider with caution in public-facing applications. https://developers.cloudflare.com/flagship/sdk/client-provid... Can anyone clarify... why the client SDK,…

Let's think about it. This is probably something used internally at CloudFlare and someone thought I'd be interesting to make it public. There is no way 6 months ago someone at CloudFlare thought it was a good idea to build a competitor to say LaunchDarkly.

Both Cloudflare and Vercel have feature parity. Flags is a feature already in Vercel. While customer-first is a thing, it is also a no-brainer to start with: we use it, Vercel has it, let us build it.

Re: Cloudflare Flagship

#34

Post by btown »

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 in a tight loop as easily and performantly as you can use a constant, it makes your business incredibly agile. Think some text might change for some customers? Just write the code to make it configurable, and you get tests and flags for free.

Sadly, that zero-hop setup requires a sophisticated client execution engine, which it doesn’t appear Cloudflare has implemented here. Makes sense for their memory constrained workers, less sense for traditional infrastructure.

Statsig has an approach here that I quite like:

> To be able to do this, Server SDKs hold the entire ruleset of your project in memory - a representation of each gate or experiment in JSON. On client SDKs, we evaluate all of the gates/experiments when you call initialize - on our servers.

https://docs.statsig.com/sdks/how-evaluation-works

You can also roll your own - just sync your rulesets to a few data structures every few seconds in a background thread and atomically swap the reference to them. Then you just need a CRUD interface over the applicability ruleset dimensions.

Just be careful to have governance on who can play with which would-be constants. Great power and great responsibility and all that!

Re: Cloudflare Flagship

#35

Post by OccamsMirror »

dboreham wrote: post #16
OsrsNeedsf2P wrote: post #14

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.

Thank you! I've never understood why this needs to be an external dependency with network requests.

Re: Cloudflare Flagship

#36

Post by NicoJuicy »

OccamsMirror wrote: post #35
dboreham wrote: post #16

Earlier quoted context omitted.

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.

Thank you! I've never understood why this needs to be an external dependency with network requests.

Deploy to master ( microservices)

Re: Cloudflare Flagship

#37

Post by elamje »

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 processing a piece of user data. Hoping Cloudflare can build a sophisticated product here so I don’t have use another product in the future!

Re: Cloudflare Flagship

#38

Post by weird-eye-issue »

wahnfrieden wrote: post #27
aetherspawn wrote: post #3

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.

Will never use them without prepayment or spending limit options. Insane to be a bug, attack, or misclick away from 6-7 digit invoice

Their pricing is not ridiculous like some providers. It would be very hard to rack up that kind of bill, especially considering their rate limiting rules are now free to use.

Re: Cloudflare Flagship

#39

Post by jjcm »

crabmusket wrote: post #22

Looking at the docs for their JS SDK, they have this warning: > The client provider requires an API token to fetch flag values. This token is not scoped to a single app, so anyone with the token can evaluate flags across all apps in your account. Use the client provider with caution in public-facing applications. https://developers.cloudflare.com/flagship/sdk/client-provid... Can anyone clarify... why the client SDK,…

Jane Wong salivating reading this

Re: Cloudflare Flagship

#40

Post by behindsight »

wahnfrieden wrote: post #27
aetherspawn wrote: post #3

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.

Will never use them without prepayment or spending limit options. Insane to be a bug, attack, or misclick away from 6-7 digit invoice

the CTO of Cloudflare (hn: dknecht) said:

> It is in the works. The billing team has been sprinting to fix a lot of debt in this area. I don’t have a date.

https://x.com/dok2001/status/2051220429973389622

Post reply on HN