Загрузка видео...

Не удалось загрузить видео

На главную

Microfrontend support in Cloudflare was my weekend project. Put many workers under a single domain with zero changes to your projects. One domain, many paths, mapped to separate Workers. / = Marketing /docs = Docs /dash = Dashboard

49,220 просмотров • 10 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

I built a self-hosted Sentry clone that runs entirely on Cloudflare Workers, and I think it showcases one of the most underrated features in the Cloudflare ecosystem: Service Bindings. Let me explain why this matters. When you have multiple Cloudflare Workers (an API, a webhook handler, a cron job), they all need common things: error tracking, authentication, rate limiting, metrics. The typical solution? External HTTP calls to third-party services. That means: - 50-200ms latency per call - Egress fees - Your data leaving your infrastructure - Another vendor to manage Service bindings let Workers call each other directly inside Cloudflare's network. No HTTP. No internet. Just internal RPC with <5ms latency. With Workers Sentinel, any Worker in my account can just point Sentry-SDK into the Service binding, and have all errors flow into one centralized dashboard, stored in Durable Objects with SQLite. No external calls. No added latency. Service bindings aren't just for error tracking. You can centralize: 🔐 Authentication — One Worker that validates tokens for all your services 📊 Metrics — Centralized collection without external observability costs 🚦 Rate Limiting — Shared counters that actually work across Workers 🚩 Feature Flags — Instant propagation, no deployment needed Think of it as building your own internal microservices mesh, but at the edge, with zero network overhead. Workers Sentinel uses two Durable Objects: - AuthState (singleton) — users, sessions, projects - ProjectState (per-project) — issues, events, stats Events are fingerprinted and grouped intelligently. The dashboard is a Vue.js app served from the same Worker. I could say i built this to learn Durable Objects or that I needed error tracking for side projects, but honestly I just need a way to show my wife why I'm sending $200/month to some guy named Claudio who apparently helps me write code. The whole thing is open source. Deploy it to your Cloudflare account, point your Sentry SDKs at it, and you're done. But more importantly: take a closer look at service bindings. They're the glue that turns a collection of Workers into an actual platform. Most Cloudflare customers I talk to aren't using them, and they're missing out. To the Sentry team: I love your work. Genuinely. Sentry is battle-tested, has incredible features, and is what you should use for anything that matters. This project is a toy. A learning exercise. A weekend hack that got slightly out of hand. Please do not trust your production errors to this dummy clone. If your startup goes down at 3 AM because Workers Sentinel missed an edge case, that's on you. I warned you. Use the real thing. But if you want to learn about Durable Objects, service bindings, and how error tracking works under the hood? Clone away. Your Workers shouldn't be islands. Connect them.

Gabriel Massadas

28,840 просмотров • 8 месяцев назад

I'm concerned we're entering a local maxima with CLIs, they're the wrong interface for agents The right interface is regular REST APIs with CIMD (same spec that MCP uses to allow for dynamic client registration) Your agent then writes code to interact with the API (like Cloudflare codemode) Think about how this works for humans today for the following action: "I want to set a DNS record on my domain" -> You Google "Vercel set DNS records" -> Docs page tells you what buttons to press -> You press buttons on a website, those call an API Now for agents, they search Google: -> "Set DNS record on Vercel Domain" -> they land on the same docs page, except it outlines what api endpoints are used as well -> the agent then calls those api endpoints for you, credentials are dynamically inserted where the agent can run them -> (optional) set auto approval policies / require approval of all non GET options by default You don't need separate interfaces for agents, nor do you really need separate skills for them CLIs have terrible discoverability, no input / output typing, they're harder to make profiles for for allowed / disallowed tools They work as a stop gap solution, but companies should be focusing on making good docs and APIs, not CLIs I've been prototyping this over at (open source if you want to play with what this world would look like - still early on it so appreciate feedback - open source and can run completely on your machine

Rhys

221,133 просмотров • 7 месяцев назад