ld-find-code-refs VS workers.cloudflare.com

Taplytics is a broad A/B testing platform for marketing teams. While DevCycle is a feature flagging tool built for developers. Taplytics actually has feature flagging, but DevCycle is much more focused and plans to compete directly with incumbents like LaunchDarkly by building a better developer experience (more on how later). But with Taplytics they built so many features and every customer was using them in a different way that it became hard for such a small team to maintain. Meanwhile, feature flagging is a much narrower problem where most customers will have similar use cases. In addition, Taplytics required lots of face-to-face time selling to executives, while DevCycle is more of a bottoms-up, self-serve sales process. Finally, we didn't cover it in the interview but feature flagging is a huge market. LaunchDarkly was valued at $3billion in 2021.

I had a custom rule added to Little Snitch that blocked the following domains: launchdarkly.com, clientstream.launchdarkly.com, mobile.launchdarkly.com

10. LaunchDarkly

There are however Saas to implement directly a feature management system. Several solutions exist like LaunchDarkly, Flagsmith or Unleash.io. Using a SaaS (Software as a Service) feature flagging solution offers the advantage of a faster and more straightforward implementation process. These services are readily available and can be quickly integrated into your project.

Currently, there are numerous feature flag systems available. Options include our own company's open-source system, "Bucketeer", and the renowned SaaS "LaunchDarkly" among others. When comparing these, the following considerations might come into play:

A variety of tools can cover some of these use cases. PLG tools like Segment and journy.io can track activity. Maybe you use a feature flag service such as LaunchDarkly. Stripe or Chargebee might manage some of the billing-related aspects. Meanwhile, problems related to authentication might be visible in your Auth0 account. However, it’s unlikely that you’re using all these platforms. Even if you are, you probably can’t cover some use cases.

If you have not used it and wonder what I am talking about: https://launchdarkly.com/.

Finding the Right Fit: I used Cloudflare Workers for the Nuxt frontend application. It is simple to use and has a generous free tier. Cloudflare also acts as your DNS manager, and offers performance optimizations and DDOS protection for free! This seems like a smart strategy on their part – support smaller projects with potential to grow, and they get word of mouth recommendations, case and point, I’m mentioning their services in this video!

Server functions may encounter performance issues due to Lambda cold starts, impacting user response time. Some providers have minimal delays (like Cloudflare Workers due to V8 engine), while others require additional steps. For instance, one way to mitigate this is by periodically invoking the server function, although this would require investigation and potential costs.

I believe you can replace most cases (static sites) with Cloudflare Workers [1].

[1] https://workers.cloudflare.com/

Cloudflare has a serverless compute platform called Workers. Workers are automatically replicated across all Cloudflare data centers, meaning that the developer can make an API or other application that automatically scales with zero infrastructure! Workers also automatically routes user requests to their nearest data center, meaning that latency is reduced significantly!

Cloudflare Workers are Cloudflare’s answer to AWS Lambda. They let you deploy serverless code instantly across the globe and are blazing fast. You write code and deploy it to cloud environments without the need for traditional infrastructure.

Cloudflare Workers

This article guides you on how to build a remote function for Slack's automation platform on Cloudflare Workers. The slack-cloudflare-workers library provides the toolset for swiftly creating such an app in TypeScript.

Both of these OSS options were designed for the Edge architecture based on Cloudflare Workers, but unfortunately, they no longer seem to be maintained.

Can't you stop endpoint execution with other tools, like CF workers/ Imperva and so on, on the CDN layer?