I'm beyond excited to announce the release of my second book, Serverless Apps on Cloudflare! 📚 For several years, I've been building applications on @Cloudflare's modern and innovative cloud developer platform. I was blown away by how simple and quick it was to develop applications, alongside how intuitive it all felt. This book is a culmination of those years learning the platform, distilled into easily-digestible chapters covering the core aspects of the platform. You'll learn everything from building an API and full-stack applications, to databases, caches, using AI, queues and so much more. By the end, you'll have a solid foundation that will allow you to build all kinds of applications with Cloudflare. The @CloudflareDev team has been adding new products and features at a rapid rate, with all the key ingredients needed for almost any application. It's all serverless, so you pay for what you use, with no servers or instances to maintain. It really comes into its own with how it all integrates together. Do you want to connect your compute to your database? It's a few lines of configuration, and your code is injected with what it needs at runtime by Cloudflare, with no need to maintain any sensitive credentials. In my opinion, this is what the likes of AWS, Azure and GCP wish their platforms were like. Sure, they are more vast in the products they offer, but Cloudflare likely has all the essential products and features you need to build great products and services without all the hassle and complexity. If you're interested in giving Cloudflare a try, and want a helping hand on the key aspects of their developer platform, you can get your hands on the early release version of the book right now via @pragprog: #cloudflare #book #coding #programming #develop #AWS #azure #gcp #serverless #architecture #software

@wireless_anon @CloudflareDev Yeah, this is definitely quite annoying I imagine. I think CF themselves, each engineer has their own account for dev for example, but this has the same problem and you have to pay $5 for each for Workers Paid too

RT @pragprog: New PragProg Author Spotlight: @_ashleypeacock chats with @pragdave link in comments below Whether it’s simplifying serv…

@lukaszbyjos @CloudflareDev Ahh I don’t think Cloudflare will go that direction in terms of things like IAM and that mess 😅 We use AWS orgs at my day job and it seems to work okay, but we also have a sizeable DevOps team who manage it

@lukaszbyjos @CloudflareDev How do they differ? Also, Cloudflare’s one isn’t known yet - so they may have used the GCP approach 😅

@mehulmpt @CloudflareDev Based on the wording, it’s already developed and it’ll be in public beta/preview at some point, so it almost definitely does happen 😅

@CloudflareDev In my excitement to post, I messed up some of the terminology - rather than separate Organizations, it's separate accounts within an Organization (e.g. staging is one account, production another, but all under one umbrella)

Aww thank you, I hope you enjoy it! If it were me, I would say yes but Pages won’t disappear anytime soon (too many users of it) and Static Asset Workers are in beta - so there might be some bugs and what not at this point, but once that hits GA (or if you’re not planning on going live soon or just want to play around) then absolutely go for Static Asset Workers!

It’s not, as Static Asset Workers were just out in beta when it went to print - the book does include static asset workers and pages still, and does touch on the above, but an expensive way to answer one question 😅 So, you can use either. Pages will slowly migrate into Static Asset Workers though, but that will take a long time I suspect. As for frameworks, for all the main ones, Cloudflare has adapters that translates from routes (in Next.js for example) to a Worker effectively. So you build the app as you normally would, Cloudflare handles the translation + deployment. Here’s a link to the framework guides for Static Asset workers and here’s for Pages - you can get started super easily with npm create cloudflare, it’ll bootstrap the app for the framework you pick!

@alperdincer @CloudflareDev Agreed, I think Cloudflare are still working out how best to market them, as they are (afaik) entirely unique and no one else really has them so it’s trickier to market & explain sometimes, but agree for sure it’d be helpful - the blog posts are probably the best sources I’d say

@alperdincer @CloudflareDev What limit are you concerned about? As you can create unlimited instances of DOs (so 1 per task, your example you’d have 20,000 DO instances)

@moesmufti @CloudflareDev Thank you, glad you liked it!

@pulik_io @CloudflareDev Yeah, and established tools must have added AI features that will be tricky to compete with (e.g. Zendesk) - but it’s a big space, might be able to carve out a space!

@pulik_io @CloudflareDev Thanks! For fun or as an actual app/product?

@martinklepsch @CloudflareDev Thank you!

This is going to depend a lot on the app and use case, but a SQLite DO is limited to 1GB currently (10GB once SQLite-backed DO’s exit beta) so there are some storage considerations (but 10GB worth of text is a lot!) I think it depends on what the app does. If you need to do cross-chat things, like let’s say summarise chat A and Chat B or… cross-query, one is going to be easier. If they are more ephemeral, I’d do per DO but it then perhaps requires more coordination (e.g. recording all DOs against a user ID so they can be shown in a list in a UI). I think unless you absolutely know there’s no chance of cross-chat requirements, I’d go for one as it seems more future-proof (as long as you know you won’t hit the storage limits, or can archive off enough later if needed). Another consideration is, are chats only for this user? What happens if you want different chats with different users, and you want real-time communication? It then becomes pretty gnarly with one DO per user, so lots to think about 😅

@marceloterreiro @peer_rich @vercel Understandable, things have come a long way - even Lambda is better with things like AWS SAM but imo Cloudflare is another level entirely

You could use Durable Object alarms for this (each DO could be a task, and the alarm will wake the DO up when it’s time to execute the task - then you reset the alarm). You could also use the newer Workflows, especially for longer tasks, as you can have a Workflow instantly sleep until it’s time to do the task as two approaches

It also depends what you run, Next.js is notorious for being difficult to run on anything that isn’t Vercel. OpenNext is making inroads, and Cloudflare I believe is supporting it but for a lot of other frameworks (Nuxt, Astro etc.) and building APIs and what not - Cloudflare’s DX is genuinely the best out there if we are talking Serverless, infinitely better than AWS Lambda

Perhaps if you used them 5 years ago and haven’t tried them since, they are rapidly gaining in the space and I think within 5 years will have made serious inroads in AWS & Co’s market share. Unless you’re doing some heavy, complex work (e.g. you need a lot of compute, a lot of memory) then I fail to see how the vast majority of websites/SaaS/APIs etc “suck” on Cloudflare