i am continously trying to find better patterns to get good results with llms effect is a good example and it combines so well with state machines on the frontend this is xstate/effect with react

Day 4 of Cloudflare's Birthday Week is a BIG one. There's so many announcements, the majority are new products or features! 🚀 K2: Kafka-like event-streaming service on the edge 🏋️‍♂️ Managed CloudflareOS 🧑‍💻 Artifacts: Open beta & Git platform competition ⚡️ Workers KV Instant: 2ms cache reads globally 📊 Cloudflare Basin: CF Data Platform goes GA 🔐 Modern cryptographic algorithms in Workers 🔎 AI Search goes GA 🤖 Sovereign AI and the fight for choice That's a lot to get through, I'll summarise each below! 🚀 K2: Kafka-like event-streaming service on the edge This is a wild one. This is not Kafka, but it is Kafka-like in its design, so much so that there is future work to make Kafka Clients work with K2. Cloudflare K2 is a serverless event-streaming service that stores durable, ordered streams backed by R2, running entirely on Cloudflare's edge network. This allows you to decouple producers from consumers. Consumers read events in batches through subscriptions, with support for parallel processing or fan-out. It's available today in public beta for anyone on the Workers Paid plan. The limits are low during beta, and there's no charge during beta either. 🏋️‍♂️ Managed CloudflareOS When CloudflareOS was announced earlier this year, it instantly became incredibly popular. Any person or company could deploy it to Cloudflare with a fews clicks. In a nutshell, it gives everyone an agent workspace within an organization, connected to your systems' data and incredibly secure. Here's what's new in CloudflareOS: - Mount Git repos and work with code - Work across Google Workspace - Export work in the formats your team uses Today, Cloudflare is opening a waitlist for a managed offering of CloudflareOS, with signup available in the links below. 🧑‍💻 Artifacts: Open beta & Git platform competition The moment a lot of you have been waiting for: Artifacts is now in open beta. Everyone can try it out for themselves, available from today! Alongside that announcement, here's what's new with Artifacts: - You can now connect an Artifacts repository to a Worker through Workers Builds - Manage Artifacts directly from Workers via the Artifacts binding - Subscribe to events happening in Artifacts via Event Subscriptions (pushed, cloned etc.) - Data jurisdictions for Artifacts repos - Metrics! See all the metrics about your repos in the dash Finally, there is a competition to build the next Git hosting platform on Artifacts. Two members from the top 3 teams will be flown to Cloudflare Connect in SF to demo + the winners get $25,000 in Cloudflare credits and an invite to the VIP Speakers dinner at Connect. ⚡️ Workers KV Instant: 2ms cache reads globally This is one of those announcements that you read, and you can't help but marvel at the engineering feat. Workers KV has been around since 2018 and is perfect for read-heavy workloads that can be eventually consistent (p99 4.4 seconds across the world), with p99 uncached reads of 290ms. What if you need it to be FAST though? That's where KV Instant comes in, backed by Cloudflare's internal KV store, Quicksilver. How fast, you might ask? p99 reads are 1.6ms (yes, milliseconds) and writes are 250ms (that's globally replicated in that time). If the key is cached, the read is instant, hence the name. The API is the same as Workers KV, with pricing that reflects its intended use as high read, low write caching: $0.20 per million reads (60% cheaper than regular KV) and $0.10 per operation for writes, plus $100 per MB, per month. It's available in private beta, with open beta planned later. 📊 Cloudflare Basin: CF Data Platform goes GA At first, this might sound like a new product - but it's actually a culmination of years of work to make Cloudflare a fully-fledge data platform. Basin brings together three key pieces of the Cloudflare data platform under one umbrella: - Pipelines, allowing you to receive events from Workers, HTTP, or Cloudflare Logpush, transform them with SQL, and write them as Apache Iceberg tables or files in R2. - Basin Catalog, which manages Iceberg metadata and automatically maintains tables to keep them fast and cost-efficient. - Basin SQL, is our serverless, distributed SQL engine for querying Apache Iceberg tables directly on Cloudflare. There's a ton more coming here, such as support for the latest Apache Iceberg spec, advanced adaptive table-maintenance strategies and much more. 🔐 Modern cryptographic algorithms in Workers Cloudflare Workers is adding support for post-quantum-resistant algorithms within Web Crypto, available today. The list includes: - ML-KEM-768 and ML-KEM-1024 for key encapsulation - ML-DSA-44, ML-DSA-65, and ML-DSA-87 for signatures - encapsulateBits(), decapsulateBits(), encapsulateKey(), and decapsulateKey() - getPublicKey() - SubtleCrypto.supports() - JWK import and export for these algorithms There's a great rundown of some of these algorithms and why they are important in the blog! 🔎 AI Search goes GA Cloudflare’s AI Search combines Workers AI, Vectorize, R2, and Browser Run into a fully managed index and retrieval pipeline As part of going GA, there's some enhancements to the product: - Multimodal embedding and retrieval, with caption-based understanding and native image retrieval - AI Search now accepts your text files (Markdown, HTML, CSV, JSON and similar) and PDFs up to 10 MiB, up from 4 MiB - OCR support is available too Alongside GA, pricing has been announced - there's many dimensions to it, and the blog below has all the info on pricing. 🤖 Sovereign AI and the fight for choice Cloudflare is bringing EuroLLM, which supports 35 languages, and Switzerland’s fully open Apertus, trained on more than 1,500 languages, to Workers AI. This matters because governments and essential services may be vulnerable if they depend on one AI provider or lose access to a model. In a nutshell, AI should be for everyone and not belong in the hands of the few. --- Today's announcements are just insane to me, there's SO much there and it's hard to fit all the detail in without this turning into a novel! What're you most exicted by?

this month the goal is to get our ci/cd to like ~5 minute per project instead of 30 minutes for our entire monorepo (which will be split up) so far the ideas are: - move internal apps from vercel to aws (so we can run blacksmith only for the entire build) - move internal apps from nextjs to tanstack start (because tanstack start fits better for those apps and vite should be faster for those projects, especially hosted on aws) - integrate backend in tanstack start as much as possible instead of deploying a ton of lambdas (will still need to deploy some lambdas for durable functions probably and event listeners) - try to move entire landing page setup onto only vercel and a nextjs project as we move from a big backend to smaller services - reduce scope of monorepo by breaking things apart to actual npm libraries - remove as many external npm libraries as possible. build our own with as many similar dependencies as possible when there is a need to share