Show HN: An edge first feature flag implementation on Cloudflare (opens in new tab)

(github.com)

4 pointsdj0k3r1y ago4 comments

FlagShip is a serverless feature flag application that you can host and manage yourself on Cloudflare. This work is the outcome of my Master's thesis where I evaluate the feasibility and performance benefits of building stateful serverless applications at the edge.

4 comments

NathanFlurry1y ago

Neat! Love the ability to deploy some like as powerful as Launch Darkly effortlessly with Workers.

D1’s read replicas [1] is still pretty new, how has this worked out for a read-heavy workload like FlagShip?

[1] https://blog.cloudflare.com/building-d1-a-global-database/#s...

dj0k3rOP1y ago

Thank you!

D1 read replication was not available when I started working on FlagShip. However, since I only use D1 for storing data like project configuration, replication was not really necessary.

The flags consumed by the clients are pushed to and read from KV alone. KV already has geo replication out of the box, although there still is propagation delay for updates to KV.

It would be nice to have everything served from D1, I might consider it when replication is stable enough.

cebert1y ago

This is a neat use of Cloudflare workers. Is there a reason you chose D1 and KV over using Durable Objects?

dj0k3rOP1y ago

Thank you. It's mostly because of costs (free tier).

I mostly use KV for storing flags specific to each project (which gets replicated automatically). Everything else goes to D1 (replication isn't needed here).

Cloudflare queues was something I might consider for async workflows.

j / k navigate · click thread line to collapse

4 comments

NathanFlurry1y ago

Neat! Love the ability to deploy some like as powerful as Launch Darkly effortlessly with Workers.

D1’s read replicas [1] is still pretty new, how has this worked out for a read-heavy workload like FlagShip?

[1] https://blog.cloudflare.com/building-d1-a-global-database/#s...

dj0k3rOP1y ago

Thank you!

D1 read replication was not available when I started working on FlagShip. However, since I only use D1 for storing data like project configuration, replication was not really necessary.

The flags consumed by the clients are pushed to and read from KV alone. KV already has geo replication out of the box, although there still is propagation delay for updates to KV.

It would be nice to have everything served from D1, I might consider it when replication is stable enough.

cebert1y ago

This is a neat use of Cloudflare workers. Is there a reason you chose D1 and KV over using Durable Objects?

dj0k3rOP1y ago

Thank you. It's mostly because of costs (free tier).

I mostly use KV for storing flags specific to each project (which gets replicated automatically). Everything else goes to D1 (replication isn't needed here).

Cloudflare queues was something I might consider for async workflows.

j / k navigate · click thread line to collapse