Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Infrastructure as Code is solved. There's no longer any excuse for a service not to have it. Here's a walkthrough of Alchemy's automated flywheel that generated 100% coverage for both AWS and Cloudflare. 1000s of Resources and Bindings, zero slop.

44,276 Aufrufe • vor 9 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Almost 20 years later, AWS is still the most popular cloud in the world. The reason is simple: it just works! They have four services focused on Generative AI: 1. Amazon Q 2. Amazon Bedrock 3. SageMaker JumpStart 4. PartyRock I've been using AWS for around 15 years (honestly, I don't remember well), and their Developer Center is a gold mine. If you open their Developer Center, you'll find a new learning path, "Generative AI for Developers." I'm linking to it below. This is not just a course. This is a collection of courses, examples, videos, tutorials, and code walkthroughs. They will teach you how to use Generative AI on AWS using the four services above. ↑ That right there is a huge selling point: These classes aren't just theoretical. You'll have a chance to learn using the same professional tools everyone else uses. By the way, there are many more resources in the Developer Center: • Machine Learning • Data Operations • DevOps All of these are free. Click, click, and start learning right away. One more thing before I forget: If you are building anything with AWS, check out Amazon Q, their coding assistant. This is the *best* coding assistant for AWS-related work, and it's not even close. It's a Visual Studio Code extension. Install it, and it works like any other code assistant, except this one knows a lot about AWS. Thanks to AWS for sponsoring a post about their free courses and learning resources. There's a special place in Developer Heaven for you.

Santiago

22,104 Aufrufe • vor 1 Jahr

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,656 Aufrufe • vor 6 Monaten