feat: add content to cloudflare roadmap (#8248)
* add content to prerequisites and core dev skills. * add content and topic links to each topic. few refractors too. ---pull/8252/head
Vedansh
2 days ago
committed by
GitHub
parent
28c41b02c0
commit
5023e962b3
90 changed files with 888 additions and 112 deletions
@ -1 +1,8 @@ |
||||
# AI Gateway |
||||
# AI Gateway |
||||
|
||||
Cloudflare's AI Gateway acts as a central point for managing and optimizing your AI workloads. It provides features like caching, rate limiting, and observability for AI requests, helping you improve performance, reduce costs, and gain insights into how your AI models are being used. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare + AI](https://ai.cloudflare.com/) |
||||
- [@official@Cloudflare AI Gateway](https://www.cloudflare.com/developer-platform/products/ai-gateway/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# AI Model Integration |
||||
# AI Model Integration |
||||
|
||||
Workers AI provides the ability to run AI models directly on Cloudflare's edge network for recognition tasks. This includes image recognition (identifying objects or scenes in images) and natural language understanding (analyzing text for sentiment, intent, or entities). By performing AI model recognition at the edge, you can reduce latency and improve the responsiveness of AI-powered applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare + AI](https://ai.cloudflare.com/) |
||||
- [@official@Cloudflare AI Model Integration](https://developers.cloudflare.com/ai-gateway/integrations/) |
||||
|
||||
@ -1 +1,14 @@ |
||||
# AI-powered Search |
||||
# AI-powered Search |
||||
|
||||
You can build AI-powered search using Cloudflare Workers, Workers AI, and Vectorize. |
||||
|
||||
1. **Embed Data:** Use Workers AI to create vector embeddings of your data (e.g., text, images). |
||||
2. **Store Embeddings:** Store these embeddings in Vectorize. |
||||
3. **Search:** When a user searches, embed the search query using Workers AI and then use Vectorize to find the most similar embeddings in your database. |
||||
4. **Return Results:** Return the corresponding data items as search results. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare + AI](https://ai.cloudflare.com/) |
||||
- [@official@Cloudflare Agents](https://developers.cloudflare.com/agents/) |
||||
- [@article@How to use Cloudflare Workers AI for building an AI-powered Search](https://dev.to/charlestehio/how-to-use-cloudflare-workers-ai-for-building-an-ai-powered-search-bar-51jn) |
||||
@ -1 +1,20 @@ |
||||
# Any Frontend Framework |
||||
# Any Frontend Framework |
||||
|
||||
Several frontend frameworks can be deployed on Cloudflare Pages or used with Cloudflare Workers. Popular choices include: |
||||
|
||||
- **React:** Deploy using Create React App or Next.js. |
||||
- **Vue.js:** Deploy using Vue CLI or Nuxt.js. |
||||
- **Angular:** Deploy using Angular CLI. |
||||
- **Svelte:** Deploy using SvelteKit. |
||||
- **Astro**: Deploy using Astro CLI. |
||||
|
||||
Cloudflare Pages offers optimized builds and deployments for these frameworks. For Workers, you can use these frameworks to render content dynamically at the edge. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@React](https://react.dev/) |
||||
- [@official@Vue.js](https://vuejs.org/) |
||||
- [@official@Angular](https://angular.dev/) |
||||
- [@official@Svelte](https://svelte.dev/) |
||||
- [@official@Astro](https://astro.build/) |
||||
- [@official@Framework Guide](https://developers.cloudflare.com/pages/framework-guides/) |
||||
@ -1 +1,8 @@ |
||||
# Asset Management |
||||
# Asset Management |
||||
|
||||
Cloudflare R2 can be used for efficient asset management. You can store images, videos, and other static assets in R2 and serve them directly through Cloudflare's CDN. This reduces the load on your origin server and improves website performance. R2's integration with Cloudflare Workers allows you to perform on-the-fly image transformations or other asset processing tasks at the edge. Versioning support in R2 helps manage different versions of your assets. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Use R2 as Static Asset Storage with Cloudflare Pages](https://developers.cloudflare.com/pages/tutorials/use-r2-as-static-asset-storage-for-pages/) |
||||
- [@official@Cloudflare R2 | Zero Egress Fee Object Storage](https://www.cloudflare.com/developer-platform/products/r2/) |
||||
@ -1 +1,8 @@ |
||||
# Background Jobs |
||||
# Background Jobs |
||||
|
||||
Cloudflare Queues are ideal for handling background jobs. Instead of performing time-consuming tasks directly within a request/response cycle, you can enqueue a message describing the task. A separate Worker, acting as a consumer, then processes these messages in the background. This improves the responsiveness of your application and allows you to handle tasks like image processing, sending emails, or data analysis without blocking user requests. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Queues](https://developers.cloudflare.com/queues/) |
||||
- [@article@Dispatched | Background Jobs for Serverless Applications](https://dispatched.dev/) |
||||
@ -1 +1,17 @@ |
||||
# Bindings |
||||
# Bindings |
||||
|
||||
In Cloudflare Workers, Bindings are configurations that connect your Worker to external resources or services. These can include: |
||||
|
||||
- **KV Namespaces:** Binding to a KV namespace allows the Worker to read and write data. |
||||
- **Durable Objects:** Bindings specify which Durable Object namespace the Worker can access. |
||||
- **Service Bindings:** Connecting to other Workers or Cloudflare services like Queues. |
||||
- **Secrets:** Storing sensitive data (API keys) securely. |
||||
- **Environment Variables:** Configuring environment-specific settings. |
||||
|
||||
Bindings are defined in the `wrangler.toml` file and provide a secure and managed way for your Worker to interact with the outside world. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Bindings (env) · Cloudflare Workers](https://developers.cloudflare.com/workers/runtime-apis/bindings/) |
||||
- [@official@Workers Bindings · Cloudflare Workers AI](https://developers.cloudflare.com/workers-ai/configuration/bindings/) |
||||
- [@official@Configuration - Wrangler · Cloudflare Workers](https://developers.cloudflare.com/workers/wrangler/configuration/) |
||||
@ -1 +1,8 @@ |
||||
# Bot Management |
||||
# Bot Management |
||||
|
||||
Cloudflare Bot Management identifies and mitigates malicious bot traffic. It uses machine learning and behavioral analysis to distinguish between human and bot activity. Cloudflare can block, challenge, or allow bot traffic based on its behavior and characteristics. This helps prevent - Credential stuffing, Content scraping, Spam submissions, DDoS attacks. Effective bot management improves website performance, security, and resource utilization. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Bot Management & Protection](https://www.cloudflare.com/application-services/products/bot-management/) |
||||
- [@official@What is Bot Management? | How Bot Managers work?](https://www.cloudflare.com/learning/bots/what-is-bot-management/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Browser Rendering |
||||
# Browser Rendering |
||||
|
||||
Cloudflare Browser Rendering allows you to render web pages in a headless browser environment on Cloudflare's edge network. This is useful for tasks like generating PDFs, taking screenshots, or pre-rendering content for SEO purposes. By performing browser rendering at the edge, you can offload processing from your origin server and improve performance for certain types of web applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Browser Rendering](https://developers.cloudflare.com/browser-rendering/) |
||||
- [@official@Browser Rendering API - Blog](https://blog.cloudflare.com/browser-rendering-api-ga-rolling-out-cloudflare-snippets-swr-and-bringing-workers-for-platforms-to-our-paygo-plans/) |
||||
@ -1 +1,8 @@ |
||||
# Bucket Lifecycle |
||||
# Bucket Lifecycle |
||||
|
||||
The lifecycle of an R2 bucket involves creation, usage (storing and retrieving objects), and eventual deletion. You create a bucket to house your data. Objects are then uploaded, accessed, and managed within the bucket. Cloudflare doesn't have built-in lifecycle rules like some other storage providers, so object expiration typically requires custom logic via Workers. Finally, when the bucket is no longer needed, and after ensuring it's empty, you can delete it. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Buckets · Cloudflare R2](https://developers.cloudflare.com/r2/buckets/) |
||||
- [@official@Bucket Lifecycle · Cloudflare R2](https://developers.cloudflare.com/api/resources/r2/subresources/buckets/subresources/lifecycle/) |
||||
@ -1 +1,15 @@ |
||||
# Bucket Operations |
||||
# Bucket Operations |
||||
|
||||
In Cloudflare R2, buckets are containers for storing objects. You can perform various bucket operations, including: |
||||
|
||||
- **Creating Buckets:** Creating new buckets to organize your data. |
||||
- **Listing Buckets:** Listing all the buckets in your account. |
||||
- **Deleting Buckets:** Deleting buckets that are no longer needed (must be empty). |
||||
- **Configuring Bucket Policies:** Setting access control policies for buckets. |
||||
|
||||
These operations are typically performed using the R2 API, the Cloudflare dashboard, or command-line tools like `wrangler`. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Buckets · Cloudflare R2](https://developers.cloudflare.com/r2/buckets/) |
||||
- [@official@Create New Buckets · Cloudflare R2](https://developers.cloudflare.com/r2/buckets/create-buckets/) |
||||
@ -1 +1,8 @@ |
||||
# Bulk Operations |
||||
# Bulk Operations |
||||
|
||||
Cloudflare Workers allow you to perform bulk operations on KV stores. You can use the `batch` method to perform multiple operations in a single request. This is useful for tasks like importing data from an external source or updating multiple records at once. Bulk operations are efficient and scalable, allowing you to handle large amounts of data with ease. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Workers KV](https://blog.cloudflare.com/workers-kv-is-ga/) |
||||
- [@official@Workers KV Runtime API](https://developers.cloudflare.com/workers/runtime-apis/kv) |
||||
@ -1 +1,7 @@ |
||||
# Cache API |
||||
# Cache API |
||||
|
||||
Cloudflare's Cache API allows Workers to programmatically control caching behavior. You can store responses in Cloudflare's global cache and retrieve them later, reducing origin server load and improving performance. The Cache API offers fine-grained control over cache keys, expiration, and other parameters. This enables you to cache dynamic content, personalize responses, and optimize content delivery for specific users or devices. The Cache API is a powerful tool for building highly performant and scalable applications on Cloudflare. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare API Cache · Cloudflare](https://developers.cloudflare.com/api-next/resources/cache//) |
||||
|
||||
@ -1 +1,15 @@ |
||||
# Caching Patterns |
||||
# Caching Patterns |
||||
|
||||
Caching is a critical aspect of building performant and scalable applications. Cloudflare Workers provide several caching patterns that you can use to optimize your application's performance. These patterns include: |
||||
|
||||
- **Cache-First:** Serve from cache if available, otherwise fetch from origin. |
||||
- **Network-First:** Always fetch from origin, caching the response for subsequent requests. |
||||
- **Stale-While-Revalidate:** Serve from cache immediately, then update the cache in the background. |
||||
|
||||
You can also manipulate HTTP cache headers (Cache-Control, Expires) to control how Cloudflare's CDN caches content. Effective caching is crucial for improving performance and reducing origin server load. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@How the Cache Works · Cloudflare Workers](https://developers.cloudflare.com/workers/reference/how-the-cache-works/) |
||||
- [@article@Caching Strategies](https://docs.aws.amazon.com/whitepapers/latest/database-caching-strategies-using-redis/caching-patterns.html) |
||||
- [@article@Caching Static and Dynamic Content](https://www.cloudflare.com/learning/cdn/caching-static-and-dynamic-content/) |
||||
|
||||
@ -1 +1,14 @@ |
||||
# Caching Strategies |
||||
# Caching Strategies |
||||
|
||||
Cloudflare Workers allow fine-grained control over caching. You can use the Cache API to store and retrieve responses directly within your Worker, bypassing the origin server. Strategies include: |
||||
|
||||
- **Cache-First:** Serve from cache if available, otherwise fetch from origin. |
||||
- **Network-First:** Always fetch from origin, caching the response for subsequent requests. |
||||
- **Stale-While-Revalidate:** Serve from cache immediately, then update the cache in the background. |
||||
|
||||
You can also manipulate HTTP cache headers (Cache-Control, Expires) to control how Cloudflare's CDN caches content. Effective caching is critical for improving performance and reducing origin server load. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cache · Cloudflare Workers](https://developers.cloudflare.com/workers/runtime-apis/cache/) |
||||
- [@official@How the Cache Works · Cloudflare Workers ](https://developers.cloudflare.com/workers/reference/how-the-cache-works/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Calls |
||||
# Calls |
||||
|
||||
Cloudflare Calls is a platform for building real-time audio and video applications directly on Cloudflare's edge network. It provides the infrastructure and APIs you need to create interactive experiences like video conferencing, live streaming, and voice chat, with low latency and global reach. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Calls](https://developers.cloudflare.com/calls/) |
||||
- [@official@Introduction · Cloudflare Calls](https://developers.cloudflare.com/calls/introduction/) |
||||
|
||||
@ -1 +1,10 @@ |
||||
# CI/CD Pipelines |
||||
# CI/CD Pipelines |
||||
|
||||
CI/CD (Continuous Integration/Continuous Deployment) pipelines automate the process of building, testing, and deploying Cloudflare Workers. Common CI/CD platforms like GitHub Actions, GitLab CI, and CircleCI can be used to create pipelines that automatically deploy Workers whenever code changes are pushed to a repository. These pipelines typically involve steps like linting, testing, building, and deploying using `wrangler`. Automating deployments ensures faster releases and reduces the risk of errors. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Automate your workflow - Github Actions](https://github.com/features/actions) |
||||
- [@official@CI/CD Pipelines - Gitlab](https://docs.gitlab.com/ee/ci/pipelines/) |
||||
- [@official@Continuous Integration and Delivery - CircleCI](https://circleci.com/) |
||||
- [@official@Simple, Flexible, Trustworthy CI/CD Tools - Travis CI](https://www.travis-ci.com/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Coordination |
||||
# Coordination |
||||
|
||||
Durable Objects facilitate coordination between different clients or Workers. Because each object has a single, consistent view of its state, it can act as a central point for coordinating actions. Multiple clients can interact with the same Durable Object, and the object can ensure that actions are performed in a consistent and predictable order. This is useful for building collaborative applications where multiple users need to work on the same data. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Durable Objects](https://www.cloudflare.com/developer-platform/products/durable-objects/) |
||||
- [@article@Durable Objects (DO)](https://www.lambrospetrou.com/articles/durable-objects-cloudflare/) |
||||
@ -1 +1,8 @@ |
||||
# D1 |
||||
# D1 |
||||
|
||||
Cloudflare D1 is a serverless SQL database designed to run on Cloudflare's edge network. It allows you to store and query data closer to your users, reducing latency and improving application performance. D1 is based on SQLite and is accessible directly from Cloudflare Workers, making it easy to build dynamic and data-driven applications without managing a traditional database server. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare D1 Documentation](https://developers.cloudflare.com/d1/) |
||||
- [@official@Getting Started with D1](https://developers.cloudflare.com/d1/get-started/) |
||||
@ -1 +1,8 @@ |
||||
# Dead Letter Queues |
||||
# Dead Letter Queues |
||||
|
||||
Dead Letter Queues (DLQs) are an important part of a robust message queuing system. In Cloudflare Queues, a DLQ is a separate queue where messages that cannot be processed successfully after multiple retries are sent. This allows you to isolate problematic messages and prevent them from causing continuous failures. You can then investigate the messages in the DLQ to identify and fix the underlying issues. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@What is DLQ? - Dead-Letter Queue Explained - AWS](https://aws.amazon.com/what-is/dead-letter-queue/) |
||||
- [@article@Dead Letter Queue](https://en.wikipedia.org/wiki/Dead_letter_queue) |
||||
|
||||
@ -1 +1,17 @@ |
||||
# Debugging Techniques |
||||
# Debugging Techniques |
||||
|
||||
Debugging Cloudflare Workers involves several techniques: |
||||
|
||||
- **Console Logging:** Using `console.log()` to output variables and track code execution. |
||||
- **`wrangler tail`:** Viewing real-time logs from your Worker in the command line. |
||||
- **Source Maps:** Mapping compiled code back to the original source for easier debugging. |
||||
- **Try-Catch Blocks:** Handling errors gracefully and logging relevant information. |
||||
- **Local Testing:** Using `wrangler dev` to test Workers locally before deployment. |
||||
|
||||
These techniques help identify and resolve issues in your Workers effectively. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Chrome DevTools](https://developer.chrome.com/docs/devtools) |
||||
- [@official@Debugging Cloudflare Workers](https://developers.cloudflare.com/workers/playground/#devtools) |
||||
- [@article@Debugging Cloudflare Workers](https://blog.cloudflare.com/debugging-cloudflare-workers/) |
||||
|
||||
@ -1 +1,7 @@ |
||||
# Development Tools |
||||
# Development Tools |
||||
|
||||
- **Wrangler:** The command-line interface (CLI) is your primary tool for interacting with Cloudflare Workers. It handles project creation, local testing, deployment, secret management, and more. Wrangler simplifies the entire development lifecycle. |
||||
- **Miniflare:** This local simulator replicates the Cloudflare Workers environment on your machine. It supports features like KV storage, Durable Objects, and the Cache API, enabling offline development and testing. |
||||
- **Cloudflare Dashboard:** The web interface provides a visual way to manage your Cloudflare account, configure settings, monitor performance, and view analytics. It's useful for managing DNS, security rules, and other global settings. |
||||
- **Workers Playground:** A browser-based environment for experimenting with Workers code. It's ideal for quick prototyping and testing small code snippets without setting up a local development environment. |
||||
- **VS Code Extension:** This extension integrates with Visual Studio Code, providing features like syntax highlighting, code completion, and debugging support for Cloudflare Workers. It enhances the development experience within your preferred IDE. |
||||
|
||||
@ -1 +1,8 @@ |
||||
# DevTools Integration |
||||
# DevTools Integration |
||||
|
||||
Cloudflare Workers can be debugged using standard browser DevTools. When running Workers in a local environment (e.g., with Miniflare), you can use Chrome DevTools or similar tools to inspect code, set breakpoints, and step through execution. You can also use `console.log` statements to output information to the DevTools console. This integration makes debugging Workers more intuitive and efficient. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Debugging Cloudflare Workers](https://developers.cloudflare.com/workers/playground/#devtools) |
||||
- [@official@Chrome DevTools](https://developer.chrome.com/docs/devtools) |
||||
|
||||
@ -1 +1,9 @@ |
||||
# DevTools |
||||
# DevTools |
||||
|
||||
While you can't directly use traditional browser DevTools with Cloudflare Workers running on the edge, you can leverage similar debugging principles. Cloudflare offers tools like `wrangler tail` for real-time logging and the ability to inspect request/response headers. Using `console.log` strategically within your Worker code and analyzing the output via `wrangler tail` is the primary way to inspect variables and execution flow, emulating some DevTools functionality. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Chrome DevTools](https://developer.chrome.com/docs/devtools) |
||||
- [@official@Overview | Chrome DevTools | Chrome for Developers](https://developer.chrome.com/docs/devtools/overview/) |
||||
- [@official@Debugging Cloudflare Workers](https://developers.cloudflare.com/workers/playground/#devtools) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Drizzle |
||||
# Drizzle |
||||
|
||||
Drizzle ORM is a TypeScript ORM (Object-Relational Mapper) that can be used with Cloudflare D1 to provide a type-safe and more developer-friendly way to interact with your database. It allows you to define your database schema using TypeScript code and provides a query builder that helps you construct SQL queries in a type-safe manner. Drizzle can simplify database interactions, improve code maintainability, and reduce the risk of SQL injection vulnerabilities. It also supports migrations, making it easier to manage schema changes over time. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Drizzle](https://orm.drizzle.team/) |
||||
- [@official@Drizzle Overview](https://orm.drizzle.team/docs/overview) |
||||
|
||||
@ -1 +1,7 @@ |
||||
# Durable Objects |
||||
# Durable Objects |
||||
|
||||
Cloudflare Durable Objects provide a strongly consistent, single-actor execution environment on Cloudflare's edge network. Unlike Workers, which are stateless, Durable Objects maintain state, enabling you to build applications that require coordination and data consistency across multiple requests and users. They are ideal for building collaborative applications, real-time games, and other stateful services. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Durable Objects - Cloudflare Docs](https://developers.cloudflare.com/durable-objects/) |
||||
|
||||
@ -1 +1,9 @@ |
||||
# Edge Computing Fundamentals |
||||
# Edge Computing Fundamentals |
||||
|
||||
Edge computing brings computation closer to the user, minimizing latency. Cloudflare Workers embodies this: your code runs on Cloudflare's global network of servers, near your users. This reduces network hops and improves response times. By executing logic at the edge, you can personalize content, filter requests, and optimize delivery without needing to route traffic back to a central server. Edge computing with Workers enables faster, more responsive applications and enhanced user experiences. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@What is Edge Computing - Cloudflare Docs](https://www.cloudflare.com/learning/serverless/glossary/what-is-edge-computing/) |
||||
- [@article@What is Edge Computing? Is It More Than a Buzzword?](https://www.howtogeek.com/devops/what-is-edge-computing-is-it-more-than-a-buzzword/) |
||||
- [@course@What Is Edge Computing? - Coursera](https://www.udemy.com/course/edge-computing/) |
||||
@ -1 +1,14 @@ |
||||
# Edge SSL/TLS |
||||
# Edge SSL/TLS |
||||
|
||||
Cloudflare's Edge SSL/TLS terminates SSL/TLS connections at Cloudflare's edge network, close to the user. This reduces latency and improves performance compared to terminating connections at the origin server. Cloudflare offers various SSL/TLS options, including: |
||||
|
||||
- **Universal SSL:** Free SSL certificates for all Cloudflare users. |
||||
- **Dedicated SSL:** Custom SSL certificates for specific domains. |
||||
- **Origin CA:** Free certificates for securing communication between Cloudflare and your origin. |
||||
|
||||
Edge SSL/TLS ensures secure communication between users and your website while optimizing performance. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Get Started with SSL/TLS - Cloudflare Docs](https://developers.cloudflare.com/ssl/get-started/) |
||||
- [@official@Edge Certificates · Cloudflare SSL/TLS](https://developers.cloudflare.com/ssl/edge-certificates/) |
||||
|
||||
@ -1 +1,9 @@ |
||||
# Email Workers |
||||
# Email Workers |
||||
|
||||
Email Workers allow you to intercept and modify email traffic passing through Cloudflare's email routing service. You can use Email Workers to perform tasks like spam filtering, email authentication, and custom email processing logic, giving you greater control over your email flow. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Email Workers · Cloudflare Email Routing](https://developers.cloudflare.com/email-routing/email-workers/) |
||||
- [@official@Route to Workers, Automate Your Email Processing](https://blog.cloudflare.com/announcing-route-to-workers/) |
||||
- [@article@Implementing an Email Delivery Service with Cloudflare Workers](https://medium.com/@georgechmr/implementing-an-email-delivery-service-with-cloudflare-workers-c141422109d0) |
||||
@ -1 +1,13 @@ |
||||
# Event-driven Architectures |
||||
# Event-driven Architectures |
||||
|
||||
Cloudflare Workers are well-suited for event-driven architectures. You can trigger Workers based on various events, such as: |
||||
|
||||
- Incoming HTTP requests |
||||
- Scheduled tasks (using Cron Triggers) |
||||
- Webhooks from external services |
||||
|
||||
This allows you to build reactive systems that respond to events in real-time. Workers can process events and trigger other actions, creating a chain reaction that automates complex tasks. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@What Is Event-Driven Architecture? - IBM](https://www.ibm.com/think/topics/event-driven-architecture) |
||||
|
||||
@ -1 +1,14 @@ |
||||
# External API Integration |
||||
# External API Integration |
||||
|
||||
Cloudflare Workers can integrate with external APIs to enrich functionality. You can use fetch() within a Worker to make requests to third-party services. This enables you to: |
||||
|
||||
- Retrieve data from external sources. |
||||
- Send data to external systems. |
||||
- Authenticate with external services using API keys or tokens. |
||||
|
||||
Integrating with external APIs allows you to build powerful applications that leverage the capabilities of other platforms. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@APIs · Cloudflare Workers](https://developers.cloudflare.com/workers/configuration/integrations/apis/) |
||||
- [@official@External Services · Cloudflare Workers](https://developers.cloudflare.com/workers/configuration/integrations/external-services/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Fetch API and Runtime APIs |
||||
# Fetch API and Runtime APIs |
||||
|
||||
Within Cloudflare Workers, the Fetch API is your primary tool for making HTTP requests to external services or your origin server. It's similar to the Fetch API in browsers but adapted for the Workers environment. Runtime APIs provide access to Cloudflare-specific features like KV storage (for persistent data), Durable Objects (for stateful applications), and other services. These APIs allow Workers to interact with Cloudflare's infrastructure and build powerful applications that go beyond simple request/response handling. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Fetch API in Workers](https://developers.cloudflare.com/workers/runtime-apis/fetch) |
||||
- [@article@Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) |
||||
|
||||
@ -1 +1,15 @@ |
||||
# Filtering |
||||
# Filtering |
||||
|
||||
In Cloudflare Email Workers, filtering is the process of selectively acting on emails based on specific criteria. It allows you to define rules that determine which emails your worker will process and how. Filtering can be based on various email attributes, including: |
||||
|
||||
- **Sender/Recipient:** Matching specific email addresses or domains. |
||||
- **Subject Line:** Looking for keywords or patterns in the subject. |
||||
- **Headers:** Examining specific header values. |
||||
- **Content:** Analyzing the email body for certain keywords. |
||||
|
||||
By implementing filtering, you can ensure that your worker only processes relevant emails, optimizing performance and preventing unintended actions on unrelated messages. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Email Workers · Cloudflare Email Routing](https://developers.cloudflare.com/email-routing/email-workers/) |
||||
- [@article@Implementing an Email Delivery Service with Cloudflare Workers](https://medium.com/@georgechmr/implementing-an-email-delivery-service-with-cloudflare-workers-c141422109d0) |
||||
|
||||
@ -1,13 +1,13 @@ |
||||
# Hono |
||||
|
||||
Hono is a small, simple and ultrafast web framework built on web standards. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Netlify, AWS Lambda, Lambda@Edge, and Node.js. Hono is more known for supporting a lot more than the basics. |
||||
Hono is a small, simple and ultra-fast web framework built on web standards. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Netlify, AWS Lambda, Lambda@Edge, and Node.js. Hono is more known for supporting a lot more than the basics. |
||||
|
||||
## Use-cases |
||||
Hono is a simple web application framework similar to the well known javascript framework Express, without a frontend. But it runs on CDN Edges and allows you to construct larger applications when combined with middleware. |
||||
|
||||
Visit the following resources to learn more: |
||||
- [@official@Official Documentation](https://hono.dev/docs/) |
||||
|
||||
- [@official@Hono Documentation](https://hono.dev/docs/) |
||||
- [@article@Hono.js: A Small Framework with Big Potential](https://medium.com/@appvintechnologies/hono-js-a-small-framework-with-big-potential-15a093fc5c07) |
||||
- [@article@Quick Start with Hono: Simple Setup Guide](https://dev.to/koshirok096/quick-start-with-hono-simple-setup-guide-bite-sized-article-lhe) |
||||
- [@opensource@Hono JS Examples](https://github.com/honojs/examples) |
||||
- [@video@Learn with me](https://www.youtube.com/watch?v=gY-TK33G6kQ) |
||||
- [@article@Quick Start with Hono: Simple Setup Guide](https://dev.to/koshirok096/quick-start-with-hono-simple-setup-guide-bite-sized-article-lhe) |
||||
- [@video@Hono JS Tutorial](https://www.youtube.com/watch?v=gY-TK33G6kQ) |
||||
|
||||
@ -1 +1,15 @@ |
||||
# HTML Rewriting |
||||
# HTML Rewriting |
||||
|
||||
HTML rewriting with Cloudflare Workers enables you to modify HTML content on the fly. You can use Workers to parse HTML, manipulate elements, and inject new content. Common use cases include: |
||||
|
||||
- A/B testing: Dynamically changing content for different users. |
||||
- Personalization: Tailoring the HTML based on user characteristics. |
||||
- Content injection: Adding analytics scripts or ads. |
||||
- Security enhancements: Removing potentially harmful code. |
||||
|
||||
HTML rewriting allows you to customize the user experience and optimize your website without modifying the origin server. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@HTMLRewriter · Cloudflare Workers](https://developers.cloudflare.com/workers/runtime-apis/html-rewriter/) |
||||
- [@official@Introducing the HTMLRewriter API to Cloudflare Workers](https://blog.cloudflare.com/introducing-htmlrewriter/) |
||||
|
||||
@ -1 +1,15 @@ |
||||
# Image Processing |
||||
# Image Processing |
||||
|
||||
Workers AI allows you to run AI models directly within Cloudflare Workers, enabling powerful image processing capabilities at the edge. You can use Workers AI to perform tasks such as: |
||||
|
||||
- Image recognition |
||||
- Object detection |
||||
- Image classification |
||||
- Image resizing and optimization |
||||
|
||||
This allows you to build intelligent applications that analyze and manipulate images in real-time, close to the user. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@How to Build an Image Generator using Workers AI](https://developers.cloudflare.com/workers-ai/tutorials/image-generation-playground/) |
||||
- [@official@Get Started with Cloudflare Images](https://developers.cloudflare.com/images/get-started/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Images |
||||
# Images |
||||
|
||||
Cloudflare Images provides comprehensive image optimization and delivery services. It automatically resizes, converts, and optimizes images for different devices and browsers, improving website performance and reducing bandwidth usage. You can also use Cloudflare Images to store and serve images directly, eliminating the need for a separate image hosting service. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Images · Cloudflare Docs](https://developers.cloudflare.com/images/) |
||||
- [@official@Get Started with Cloudflare Images](https://developers.cloudflare.com/images/get-started/) |
||||
|
||||
@ -1 +1,16 @@ |
||||
# Integration & Workflows |
||||
# Integration & Workflows |
||||
|
||||
Workflows refers to the automated processes you can create to manage and respond to various events or conditions. This often involves chaining together different Cloudflare features and potentially integrating with external services. Workflows enable you to automate tasks such as: |
||||
|
||||
- Responding to security threats |
||||
- Optimizing website performance |
||||
- Managing user access |
||||
- Enforcing compliance policies |
||||
|
||||
Cloudflare's strength lies in its ability to integrate various services and create automated workflows. You can connect Cloudflare with external platforms using webhooks or APIs. Workflows can automate tasks like responding to security events, optimizing performance based on real-time data, or managing user access. By integrating different components, you can build complex and efficient systems that leverage Cloudflare's global network. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@CI/CD · Cloudflare Workers](https://developers.cloudflare.com/workers/ci-cd/) |
||||
- [@official@Cloudflare Workflows](https://developers.cloudflare.com/workflows/) |
||||
- [@official@Workers Builds: Integrated CI/CD built on the Workers platform](https://blog.cloudflare.com/workers-builds-integrated-ci-cd-built-on-the-workers-platform/) |
||||
|
||||
@ -1 +1,14 @@ |
||||
# Inter Worker Communication |
||||
# Inter Worker Communication |
||||
|
||||
Inter-Worker communication enables different Cloudflare Workers to interact and share data. This can be achieved through: |
||||
|
||||
- **Durable Objects:** Workers can share persistent data and coordinate state using Durable Objects. |
||||
- **KV Storage:** Workers can read and write data to a shared KV namespace. |
||||
- **Webhooks:** One Worker can trigger another by sending a webhook request. |
||||
|
||||
These methods allow you to build complex applications where different Workers handle specific tasks and collaborate to achieve a common goal. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@How Workers for Platforms works - Cloudflare Docs](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/) |
||||
- [@article@Cooperation between Cloudflare Workers](https://dev.to/chimame/cooperation-between-cloudflare-workers-has-become-amazing-thanks-to-rpc-support-4co9) |
||||
@ -1 +1,8 @@ |
||||
# Isolates Architecture |
||||
# Isolates Architecture |
||||
|
||||
Cloudflare's isolated architecture for Workers relies on lightweight V8 isolates. Each Worker runs in its own isolate, providing strong isolation from other Workers and the underlying infrastructure. Isolates start quickly and consume minimal resources, enabling rapid scaling. This architecture prevents code from one Worker from impacting others, enhancing security and stability. The isolation ensures that even if a Worker contains vulnerabilities, it cannot compromise the entire Cloudflare network or other customers' applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Reference Architectures · Cloudflare Reference Architecture](https://developers.cloudflare.com/reference-architecture/) |
||||
- [@official@Cloudflare Security Architecture](https://developers.cloudflare.com/reference-architecture/architectures/security/) |
||||
|
||||
@ -1,19 +1,8 @@ |
||||
# Itty Router |
||||
|
||||
Itty Router is a lightweight router with the motto "less is more" that supports Cloudflare workers and pages. While other libraries may suffer from feature creep/bloat to please a wider audience, Itty Router painfully consider every single byte added to itty. Our router options range from ~450 bytes to ~970 bytes for a batteries-included version with built-in defaults, error handling, formatting, etc. On top of that, the following concepts aim to keep YOUR code tiny (and readable) as well. |
||||
|
||||
## Simple Projects ideas |
||||
Itty Router is a lightweight router system that supports typescript. You can create easy and good routers for Cloudflare workers or pages. |
||||
With a simple project like a URL shortener, you can use Itty Router and Cloudflare KV. |
||||
|
||||
Other project ideas can be found: |
||||
- Webhook Relay |
||||
- Transform webhook data or API data towards another API so you can transform the data as you like. |
||||
- Micro URL Monitoring |
||||
- Monitor any URL and give back responses on the specific endpoint. |
||||
- Single-Use Download Links (Watch out for costs from Cloudflare!) |
||||
- Generate links that expire after one download, ideal for file sharing. |
||||
Itty Router is a lightweight router with the motto "less is more" that supports Cloudflare workers and pages. While other libraries may suffer from feature creep/bloat to please a wider audience, Itty Router painfully consider every single byte added to Itty. Our router options range from ~450 bytes to ~970 bytes for a batteries-included version with built-in defaults, error handling, formatting, etc. On top of that, the following concepts aim to keep YOUR code tiny (and readable) as well. |
||||
|
||||
Visit the following resources to learn more: |
||||
- [@official@Official Documentation](https://itty.dev/itty-router/) |
||||
|
||||
- [@official@ITTy Documentation](https://itty.dev/itty-router/) |
||||
- [@official@Getting Started with Itty Router](https://itty.dev/itty-router/getting-started) |
||||
@ -1 +1,9 @@ |
||||
# Key-value Operations |
||||
# Key-value Operations |
||||
|
||||
Cloudflare Workers provide a simple API for reading and writing data to a Key-Value store. You can use the `put` method to store data, and the `get` method to retrieve it. The `delete` method allows you to remove data from the store. KV stores are ideal for storing configuration data, user sessions, and other data that needs to be accessed quickly. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Read Key Value Pairs](https://developers.cloudflare.com/kv/api/read-key-value-pairs/) |
||||
- [@official@Cloudflare KV Binding API](https://developers.cloudflare.com/workers/runtime-apis/kv) |
||||
- [@official@Cloudflare Workers KV — Cloudflare Docs](https://developers.cloudflare.com/workers/runtime-apis/kv/) |
||||
@ -1 +1,15 @@ |
||||
# Large File Handling |
||||
# Large File Handling |
||||
|
||||
Handling large files on Cloudflare requires strategies to avoid exceeding size limits and ensure efficient delivery. Techniques include: |
||||
|
||||
- **Streaming:** Processing files in chunks to reduce memory usage. |
||||
- **Range Requests:** Serving only the requested portion of a file. |
||||
- **Cloudflare Stream:** Using Cloudflare's video streaming service for large video files. |
||||
- **R2 integration:** Storing large files in R2 and serving them via Workers. |
||||
|
||||
These methods allow you to handle large files effectively while leveraging Cloudflare's global network. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Resumable and Large Files · Cloudflare Stream](https://developers.cloudflare.com/stream/uploading-videos/resumable-uploads/) |
||||
- [@official@Cloudflare R2 Limits](https://developers.cloudflare.com/r2/platform/limits/) |
||||
@ -1 +1,8 @@ |
||||
# Live streaming |
||||
# Live streaming |
||||
|
||||
Cloudflare Stream supports live streaming. You can use tools like OBS Studio or Wirecast to stream video to Cloudflare, and Stream will handle the encoding, distribution, and playback. This allows you to easily broadcast live events to a global audience. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Stream](https://www.cloudflare.com/developer-platform/products/cloudflare-stream/) |
||||
- [@official@Serverless Live Streaming with Cloudflare Stream](https://blog.cloudflare.com/stream-live/) |
||||
@ -1 +1,8 @@ |
||||
# Logging and Monitoring |
||||
# Logging and Monitoring |
||||
|
||||
Effective logging and monitoring are crucial for understanding and debugging Cloudflare Workers. You can use `console.log` for basic logging during development. For production, consider using a dedicated logging service to collect and analyze logs from your Workers. Cloudflare provides metrics like request counts, CPU usage, and error rates that can be monitored in the Cloudflare dashboard. Setting up alerts based on these metrics helps you identify and address issues quickly. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Logging vs Monitoring: What's the Difference?](https://toxigon.com/logging-vs-monitoring-whats-the-difference) |
||||
- [@official@Debugging and Logging · Cloudflare Pages](https://developers.cloudflare.com/pages/functions/debugging-and-logging/) |
||||
@ -1 +1,9 @@ |
||||
# Message Processing |
||||
# Message Processing |
||||
|
||||
With Cloudflare Queues, message processing involves sending messages to a queue from a producer (usually a Worker) and then consuming those messages from the queue by a consumer (another Worker or service). The consumer processes each message, performing tasks like data transformation, calling APIs, or updating databases. Queues guarantees at-least-once delivery, meaning a message will be delivered to a consumer at least once, even if there are failures. Consumers can acknowledge successful processing to remove messages from the queue. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Queues · Cloudflare Queues](https://developers.cloudflare.com/queues/) |
||||
- [@official@How Does Queues Work?](https://developers.cloudflare.com/queues/reference/how-queues-works/) |
||||
- [@article@Difference Between Stream Processing and Message Processing](https://stackoverflow.com/questions/41744506/difference-between-stream-processing-and-message-processing) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Metadata Handling |
||||
# Metadata Handling |
||||
|
||||
Cloudflare Workers allow you to access metadata about the request, including the request method, URL, headers, and more. You can use this metadata to customize your application's behavior or to implement features like caching, authentication, or rate limiting. Metadata is available in both the `fetch` event and the `scheduled` event. It's a powerful tool for building dynamic and adaptive applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Request and Response](https://developers.cloudflare.com/workers/runtime-apis/request) |
||||
- [@official@Scheduled Event Handler](https://developers.cloudflare.com/workers/runtime-apis/scheduled-event) |
||||
@ -1 +1,8 @@ |
||||
# Middleware Patterns |
||||
# Middleware Patterns |
||||
|
||||
Middleware patterns in Cloudflare Workers allow you to chain functions to process requests or responses in a modular way. Each middleware function performs a specific task (e.g., authentication, logging, header modification) before passing the request/response to the next function in the chain. This promotes code reusability, separation of concerns, and easier maintenance. By composing middleware, you can build complex request processing pipelines. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Middleware · Cloudflare Pages](https://developers.cloudflare.com/pages/functions/middleware/) |
||||
- [@article@A Middleware Architecture for Cloudflare Workers](https://boxesplusarrows.com/blog/a-middleware-architecture-for-cloudflare-workers/) |
||||
@ -1 +1,8 @@ |
||||
# Migrations |
||||
# Migrations |
||||
|
||||
As your application evolves, your database schema will likely need to change. Database migrations provide a structured way to apply these changes in a controlled and repeatable manner. In D1, you'll typically write SQL scripts that contain the necessary `ALTER TABLE` statements to modify your schema (e.g., adding new columns, renaming columns, changing data types). You can then use `wrangler` or a similar tool to execute these migration scripts against your D1 database. It's important to version your migration scripts and apply them in the correct order to avoid data inconsistencies or errors. Consider using a migration management tool to track and apply migrations more effectively. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Database Migrations: What are the Types of DB Migrations?](https://www.prisma.io/dataguide/types/relational/what-are-database-migrations) |
||||
- [@article@Database Migrations in the Real World](https://blog.jetbrains.com/idea/2025/02/database-migrations-in-the-real-world/) |
||||
@ -1 +1,8 @@ |
||||
# Miniflare |
||||
# Miniflare |
||||
|
||||
Miniflare is a local simulator for Cloudflare Workers. It mimics the Cloudflare Workers runtime environment on your local machine, allowing you to test your Workers without deploying them to Cloudflare. Miniflare supports features like KV storage, Durable Objects, and Service Bindings, making it a valuable tool for local development and debugging. It speeds up development cycles by providing a fast and reliable local testing environment. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Miniflare - Cloudflare Workers](https://developers.cloudflare.com/workers/testing/miniflare/) |
||||
- [@opensource@cloudflare/miniflare](https://github.com/cloudflare/miniflare) |
||||
@ -1 +1,8 @@ |
||||
# Miniflare |
||||
# Miniflare |
||||
|
||||
Miniflare is a simulator for Cloudflare Workers that allows you to test your Workers locally. It mimics the Cloudflare Workers runtime environment, including features like KV storage, Durable Objects, and the Cache API. Miniflare enables rapid iteration and debugging without deploying to Cloudflare's edge network. It's a valuable tool for developing and testing Workers offline or in a controlled environment. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Miniflare - Cloudflare Workers](https://developers.cloudflare.com/workers/testing/miniflare/) |
||||
- [@opensource@cloudflare/miniflare](https://github.com/cloudflare/miniflare) |
||||
@ -1 +1,15 @@ |
||||
# Monitoring Tools |
||||
# Monitoring Tools |
||||
|
||||
Monitoring tools provide insights into the performance and health of your Cloudflare applications. Cloudflare offers built-in analytics, but you can also integrate with external monitoring services like Datadog, New Relic, or Prometheus. These tools allow you to track metrics such as: |
||||
|
||||
- Request latency |
||||
- Error rates |
||||
- Cache hit ratio |
||||
- Resource usage |
||||
|
||||
By monitoring these metrics, you can identify performance bottlenecks, detect security threats, and ensure your applications are running smoothly. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Application Performance Monitoring Tools](https://www.cloudflare.com/application-services/solutions/app-performance-monitoring/) |
||||
- [@official@Network Monitoring Tools](https://www.cloudflare.com/network-services/solutions/network-monitoring-tools/) |
||||
@ -1 +1,8 @@ |
||||
# Object Storage |
||||
# Object Storage |
||||
|
||||
Cloudflare R2 is object storage that offers fast, reliable, and affordable storage without egress fees. It's designed to work seamlessly with Cloudflare Workers, allowing you to store and retrieve data close to your users. R2 is ideal for storing static assets, user-generated content, and other data that needs to be accessed quickly and frequently. Its lack of egress fees makes it a cost-effective alternative to traditional cloud storage providers. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@What is Object Storage?](https://www.cloudflare.com/learning/cloud/what-is-object-storage/) |
||||
- [@official@Cloudflare R2 | Zero Egress Fee Object Storage](https://www.cloudflare.com/developer-platform/products/r2/) |
||||
@ -1 +1,7 @@ |
||||
# Pages Functions |
||||
# Pages Functions |
||||
|
||||
Pages Functions, (now part of Cloudflare Functions), allow you to run serverless code directly within your Cloudflare Pages projects. This lets you add dynamic functionality, like form handling or API endpoints, to your otherwise static sites. They're deployed alongside your static assets and execute on Cloudflare's edge network, ensuring low latency and high performance. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Functions · Cloudflare Pages](https://developers.cloudflare.com/pages/functions/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Persistence |
||||
# Persistence |
||||
|
||||
Durable Objects offer built-in persistence. Data stored within a Durable Object is automatically persisted to Cloudflare's storage infrastructure. You don't need to explicitly save or load data; the Durable Object handles persistence automatically. This simplifies development and ensures that your application's state is durable and reliable, even in the face of server failures. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Access Durable Objects Storage - Cloudflare Docs](https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/) |
||||
- [@official@In-memory State in a Durable Object](https://developers.cloudflare.com/durable-objects/reference/in-memory-state/) |
||||
@ -1 +1,8 @@ |
||||
# Prisma |
||||
# Prisma |
||||
|
||||
Prisma is a popular open-source ORM that provides a type-safe database client and migration tools. While not directly compatible with Cloudflare D1 due to its reliance on specific database adapters, Prisma can be used in conjunction with a D1 adapter or a custom data access layer within your Cloudflare Workers. This approach allows you to leverage Prisma's type safety, query builder, and migration features while still using D1 as your database. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Prisma](https://www.prisma.io/) |
||||
- [@official@Prisma Documentation](https://www.prisma.io/docs) |
||||
@ -1 +1,15 @@ |
||||
# Processing |
||||
# Processing |
||||
|
||||
With Cloudflare Email Workers, processing involves manipulating or analyzing incoming email content. After an email is routed to your worker, you can access and modify various aspects of the email, such as headers, body, and attachments. Processing can include tasks like: |
||||
|
||||
- **Content Modification:** Altering the email body, adding disclaimers, or translating content. |
||||
- **Data Extraction:** Parsing information from the email to use in other applications. |
||||
- **Spam Filtering:** Implementing custom spam detection logic. |
||||
- **Attachment Handling:** Processing or storing attachments. |
||||
|
||||
Email Workers provide the flexibility to customize how emails are handled, enabling a wide range of email-based applications and integrations. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Email Workers · Cloudflare Email Routing](https://developers.cloudflare.com/email-routing/email-workers/) |
||||
- [@official@Email Workers Routing - Runtime API](https://developers.cloudflare.com/email-routing/email-workers/runtime-api/) |
||||
@ -1 +1,13 @@ |
||||
# Query Optimization |
||||
# Query Optimization |
||||
|
||||
Optimizing your SQL queries is crucial for achieving good performance with Cloudflare D1, especially as your database grows. D1 leverages SQLite's query optimizer, which automatically attempts to find the most efficient way to execute your queries. However, you can significantly improve performance by following best practices: |
||||
|
||||
- **Use Indexes:** Indexes are essential for speeding up queries that filter or sort data. Create indexes on columns that are frequently used in `WHERE` clauses, `JOIN` conditions, and `ORDER BY` clauses. |
||||
- **Avoid Full Table Scans:** Full table scans can be slow, especially on large tables. Ensure your queries are using indexes to narrow down the number of rows that need to be examined. |
||||
- **Write Efficient SQL:** Use appropriate `JOIN` types, avoid using `SELECT *` (specify the columns you need), and use `WHERE` clauses to filter data as early as possible. |
||||
- **Analyze Query Performance:** Use SQLite's `EXPLAIN QUERY PLAN` command to analyze how your queries are being executed. This can help you identify potential bottlenecks and areas for improvement. |
||||
- **Consider Denormalization:** In some cases, denormalizing your database schema (adding redundant data to avoid joins) can improve query performance, but it comes at the cost of increased storage space and potential data inconsistencies. Weigh the trade-offs carefully. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Query Parameters and Cached Responses](https://developers.cloudflare.com/automatic-platform-optimization/reference/query-parameters/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Queues |
||||
# Queues |
||||
|
||||
Cloudflare Queues is a message queuing service that allows you to decouple different parts of your application. It enables you to reliably send and receive messages between Workers or other services. This asynchronous communication is useful for tasks like background processing, handling spikes in traffic, and building resilient applications. Queues ensures messages are delivered, even if the receiving service is temporarily unavailable. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Queues · Cloudflare Queues](https://developers.cloudflare.com/queues/) |
||||
- [@official@How Does Queues Work?](https://developers.cloudflare.com/queues/reference/how-queues-works/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# R2 Storage |
||||
# R2 Storage |
||||
|
||||
Cloudflare R2 Storage is a distributed object storage service that offers fast, reliable, and affordable storage without egress fees. It's designed to compete with services like Amazon S3 and Google Cloud Storage. R2 allows you to store large amounts of unstructured data (images, videos, documents) and access it quickly from anywhere in the world via Cloudflare's global network. Its key advantage is the absence of egress bandwidth charges, making it cost-effective for applications with high data retrieval needs. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare R2 | Zero Egress Fee Object Storage](https://www.cloudflare.com/developer-platform/products/r2/) |
||||
- [@official@Cloudflare R2 Documentation](https://developers.cloudflare.com/r2/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Rate Limiting |
||||
# Rate Limiting |
||||
|
||||
Cloudflare Queues can be used to implement rate limiting. Instead of directly processing every request, you can enqueue them. A consumer Worker then processes messages from the queue at a controlled rate. This prevents your backend systems from being overwhelmed by sudden spikes in traffic. You can adjust the consumer's processing rate to match the capacity of your backend services. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Queues - Queues & Rate Limits](https://developers.cloudflare.com/queues/tutorials/handle-rate-limits/) |
||||
- [@official@Rate Limiting Best Practices - Cloudflare Docs](https://developers.cloudflare.com/waf/rate-limiting-rules/best-practices/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Rate Limiting |
||||
# Rate Limiting |
||||
|
||||
Cloudflare Queues can be used to implement rate limiting. Instead of directly processing every request, you can enqueue them. A consumer Worker then processes messages from the queue at a controlled rate. This prevents your backend systems from being overwhelmed by sudden spikes in traffic. You can adjust the consumer's processing rate to match the capacity of your backend services. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Queues - Queues & Rate Limits](https://developers.cloudflare.com/queues/tutorials/handle-rate-limits/) |
||||
- [@official@Rate Limiting Best Practices - Cloudflare Docs](https://developers.cloudflare.com/waf/rate-limiting-rules/best-practices/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Request/Response Handling |
||||
# Request/Response Handling |
||||
|
||||
Cloudflare Workers excel at intercepting and modifying HTTP requests and responses. When a request hits Cloudflare, a Worker can inspect the request details (headers, URL, method) and take actions: rewrite the URL, modify headers, or even serve a completely different response. Similarly, Workers can intercept responses from the origin server, modifying the content, adding headers for caching, or even serving a cached version directly. This level of control allows for powerful customization and optimization of web traffic. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Request and Response](https://developers.cloudflare.com/workers/runtime-apis/request) |
||||
- [@article@Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) |
||||
|
||||
@ -1 +1,7 @@ |
||||
# Routing |
||||
# Routing |
||||
|
||||
In Cloudflare Email Workers, routing refers to directing incoming emails to the appropriate destination or processing logic. Email Workers intercept emails and use defined rules to determine their fate. You can route emails based on sender, recipient, subject, or other criteria. This allows you to forward emails, trigger custom logic, or even discard unwanted messages. Effective routing is critical for managing email flow, implementing custom email workflows, and building applications that react to incoming email. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Email Workers · Cloudflare Email Routing](https://developers.cloudflare.com/email-routing/email-workers/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Schema Management |
||||
# Schema Management |
||||
|
||||
Managing the structure of your database in Cloudflare D1 involves defining tables, columns, data types, primary keys, foreign keys, and indexes using standard SQL Data Definition Language (DDL) statements. Since D1 is based on SQLite, you'll use SQLite-compatible syntax. Tools like `wrangler` provide commands to execute SQL scripts, allowing you to create and modify your database schema. You'll typically start by designing your schema based on your application's data requirements and then translate that design into SQL DDL statements. Careful consideration should be given to data types to ensure data integrity and efficiency. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Schema Validation · Cloudflare API Shield](https://developers.cloudflare.com/api-shield/security/schema-validation/) |
||||
- [@official@Configure Schema Validation · Cloudflare API Shield](https://developers.cloudflare.com/api-shield/security/schema-validation/configure/) |
||||
@ -1 +1,24 @@ |
||||
# Security & Performance |
||||
# Security & Performance |
||||
|
||||
Cloudflare significantly enhances both security and performance through its global network. It provides robust protection against DDoS attacks, bot traffic, and other web threats, while also accelerating website loading times via its CDN and caching mechanisms. By terminating SSL/TLS connections at the edge and optimizing content delivery, Cloudflare ensures a secure and fast experience for users, reducing latency and improving overall website resilience. |
||||
|
||||
**Security:** Cloudflare Email Workers can enhance email security by: |
||||
|
||||
- **Spam and Phishing Detection:** Implementing custom filters to identify and block malicious emails before they reach the recipient. |
||||
- **Content Sanitization:** Removing potentially harmful content from emails, such as malicious scripts or links. |
||||
- **Authentication:** Verifying sender authenticity to prevent spoofing and phishing attacks. |
||||
- **Data Loss Prevention (DLP):** Preventing sensitive information from being sent via email. |
||||
|
||||
**Performance:** Email Workers impact performance by: |
||||
|
||||
- **Reduced Latency:** Processing emails closer to the user, minimizing delays. |
||||
- **Scalability:** Handling large volumes of email traffic without performance degradation. |
||||
- **Custom Routing:** Efficiently directing emails to the appropriate destination. |
||||
- **Optimized Processing:** Performing lightweight email processing tasks to avoid bottlenecks. |
||||
|
||||
Effectively leveraging Email Workers for security and performance requires careful planning and implementation of relevant filters, rules, and processing logic. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Application Security & Performance Solutions - Cloudflare](https://www.cloudflare.com/application-services/solutions/) |
||||
- [@official@Cloudflare Security Architecture](https://developers.cloudflare.com/reference-architecture/architectures/security/) |
||||
@ -1 +1,7 @@ |
||||
# Service Bindings |
||||
# Service Bindings |
||||
|
||||
Service Bindings allow Cloudflare Workers to seamlessly integrate with other Cloudflare services. They provide a secure and efficient way for a Worker to access resources like KV storage, Durable Objects, R2 storage, and other Workers. Instead of using API keys or direct network calls, Service Bindings create a direct connection between your Worker and the bound service, simplifying configuration and improving performance. They're essential for building complex applications that leverage the full power of the Cloudflare ecosystem. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Service Bindings · Cloudflare](https://developers.cloudflare.com/workers/platform/service-bindings/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Service Bindings |
||||
# Service Bindings |
||||
|
||||
Service Bindings allow Cloudflare Workers to seamlessly integrate with other Cloudflare services. They provide a secure and efficient way for a Worker to access resources like KV storage, Durable Objects, R2 storage, and other Workers. Instead of using API keys or direct network calls, Service Bindings create a direct connection between your Worker and the bound service, simplifying configuration and improving performance. They're essential for building complex applications that leverage the full power of the Cloudflare ecosystem. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Service Bindings - Runtime APIs](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/) |
||||
- [@official@Service Bindings · Cloudflare](https://developers.cloudflare.com/workers/platform/service-bindings/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Similarity Search |
||||
# Similarity Search |
||||
|
||||
Cloudflare offers Vectorize, a vector database, which enables similarity search. You can embed data (text, images, audio) as vectors and then use Vectorize to find the most similar vectors based on a query vector. This is used for recommendation systems, content discovery, and other applications where finding similar items is important. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Vectorize - Cloudflare](https://developers.cloudflare.com/vectorize/) |
||||
- [@opensource@seemueller-io/hyphalbase](https://github.com/seemueller-io/hyphalbase) |
||||
@ -1 +1,7 @@ |
||||
# Speech Rcognition |
||||
# Speech Recognition |
||||
|
||||
You can use Workers AI to run speech-to-text models directly on Cloudflare's edge network, enabling real-time transcription of audio data. This can be useful for applications like voice search, voice commands, and live captioning. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Whisper - Cloudflare Workers AI](https://developers.cloudflare.com/workers-ai/models/whisper/) |
||||
@ -1 +1,8 @@ |
||||
# State Management |
||||
# State Management |
||||
|
||||
Durable Objects excel at state management. Each Durable Object instance has its own persistent storage and can maintain state across multiple requests. You can store data within a Durable Object and access it consistently, regardless of which Cloudflare edge server handles the request. This eliminates the need for external databases or caching layers for managing application state. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@What are Durable Objects? - Cloudflare Documentation](https://developers.cloudflare.com/durable-objects/what-are-durable-objects/) |
||||
- [@official@Durable Object State · Cloudflare Durable Objects](https://developers.cloudflare.com/durable-objects/api/state/) |
||||
@ -1 +1,8 @@ |
||||
# Stream |
||||
# Stream |
||||
|
||||
Cloudflare Stream is a video streaming platform that makes it easy to upload, encode, and deliver videos globally. It handles all the complexities of video streaming, including encoding for different devices and network conditions, providing a reliable and high-quality viewing experience. Stream integrates seamlessly with Cloudflare's CDN, ensuring fast and efficient video delivery to users around the world. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Stream - Cloudflare Documentation](https://www.cloudflare.com/developer-platform/products/cloudflare-stream/) |
||||
- [@official@Cloudflare Stream - Cloudflare Blog](https://blog.cloudflare.com/tag/cloudflare-stream/) |
||||
@ -1 +1,9 @@ |
||||
# Testing Frameworks |
||||
# Testing Frameworks |
||||
|
||||
Testing frameworks are crucial for ensuring Cloudflare Workers function correctly. Popular options include Jest, Mocha, and Chai. These frameworks allow you to write unit tests, integration tests, and end-to-end tests for your Workers. You can simulate Cloudflare's environment and test how your Worker responds to different requests and events. Thorough testing helps identify and fix bugs early in the development process, ensuring the reliability of your Workers. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Testing - Cloudflare Workers Docs](https://developers.cloudflare.com/workers/testing/) |
||||
- [@article@Jest - Delightful JavaScript Testing](https://jestjs.io/) |
||||
- [@article@Vitest - A Fast JavaScript Test Runner](https://vitest.dev/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Text Generation |
||||
# Text Generation |
||||
|
||||
Workers AI allows you to perform text generation tasks directly on Cloudflare's edge network. You can use pre-trained models or fine-tune your own models to generate text for various purposes, such as content creation, chatbot responses, or language translation. Running text generation at the edge reduces latency and improves the responsiveness of your AI-powered applications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Choose the Right Text Generation Model](https://developers.cloudflare.com/workers-ai/tutorials/how-to-choose-the-right-text-generation-model/) |
||||
- [@official@Prompting · Cloudflare Workers AI](https://developers.cloudflare.com/workers-ai/guides/prompting/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Transactional Operations |
||||
# Transactional Operations |
||||
|
||||
Durable Objects support transactional operations. You can perform multiple operations within a single transaction, ensuring that either all operations succeed or none of them do. This helps maintain data consistency and prevents partial updates. If an error occurs during a transaction, the Durable Object automatically rolls back all changes, leaving the data in a consistent state. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Durable Object Storage · Cloudflare Durable Objects](https://developers.cloudflare.com/durable-objects/api/storage-api/) |
||||
- [@official@Transactional Storage · Cloudflare Durable Objects](https://developers.cloudflare.com:2096/durable-objects/api/transactional-storage-api/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Tunnels |
||||
# Tunnels |
||||
|
||||
Cloudflare Tunnel creates a secure, outbound-only connection between your origin server and Cloudflare's network, without opening any inbound ports. This protects your origin from direct attacks and simplifies network configuration. You can use Cloudflare Tunnel to securely expose web applications, APIs, and other services to the internet, without compromising security. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Tunnel · Cloudflare Zero Trust](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/) |
||||
- [@official@Ridiculously easy to use Tunnels - The Cloudflare Blog](https://blog.cloudflare.com/ridiculously-easy-to-use-tunnels/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Vector Embeddings |
||||
# Vector Embeddings |
||||
|
||||
Cloudflare Vectorize allows you to store and query high-dimensional vectors, often used in machine learning for tasks like similarity search and recommendation engines. By using Vectorize with Workers AI, you can build applications that perform real-time AI-powered searches and recommendations directly on Cloudflare's edge network. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Vector Database - Cloudflare Docs](https://developers.cloudflare.com/vectorize/reference/what-is-a-vector-database/) |
||||
- [@official@Cloudflare Vectorize](https://developers.cloudflare.com/vectorize/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Vectorize |
||||
# Vectorize |
||||
|
||||
Cloudflare Vectorize is a vector database that lets you store and query high-dimensional vectors, often used in machine learning for tasks like similarity search and recommendation engines. By using Vectorize with Workers AI, you can build applications that perform real-time AI-powered searches and recommendations directly on Cloudflare's edge network. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Introduction to Vectorize - Cloudflare Docs](https://developers.cloudflare.com/vectorize/get-started/intro/) |
||||
- [@official@Cloudflare Vectorize](https://developers.cloudflare.com/vectorize/) |
||||
|
||||
@ -1 +1,16 @@ |
||||
# Video Delivery |
||||
# Video Delivery |
||||
|
||||
Cloudflare Stream provides a comprehensive solution for video delivery: |
||||
|
||||
- **Encoding:** Automatically encodes videos for different devices and bandwidths. |
||||
- **Storage:** Stores your videos securely. |
||||
- **CDN:** Delivers videos globally via Cloudflare's CDN for fast playback. |
||||
- **Player:** Provides a customizable video player. |
||||
|
||||
This simplifies the process of delivering high-quality video experiences. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Delivering Videos with Cloudflare](https://developers.cloudflare.com/support/more-dashboard-apps/cloudflare-stream/delivering-videos-with-cloudflare/) |
||||
- [@official@Stream Delivery - Cloudflare Stream](https://www.cloudflare.com/application-services/solutions/stream-delivery/) |
||||
- [@official@Cloudflare Stream - Cloudflare](https://www.cloudflare.com/developer-platform/products/cloudflare-stream/) |
||||
|
||||
@ -1 +1,13 @@ |
||||
# Video Processing |
||||
# Video Processing |
||||
|
||||
Cloudflare offers video processing capabilities through Stream and Workers: |
||||
|
||||
- **Stream:** Handles encoding, transcoding, and adaptive bitrate streaming automatically. |
||||
- **Workers:** You can use Workers to intercept video requests and perform custom processing, such as adding watermarks or modifying metadata. |
||||
|
||||
This allows you to customize your video delivery pipeline. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Stream - Cloudflare](https://www.cloudflare.com/developer-platform/products/cloudflare-stream/) |
||||
- [@official@VOD Platform | Video-on-demand Streaming Software](https://www.cloudflare.com/developer-platform/solutions/video-on-demand/) |
||||
@ -1 +1,16 @@ |
||||
# Web Security Headers |
||||
# Web Security Headers |
||||
|
||||
Web security headers are HTTP response headers that enhance website security. Cloudflare allows you to easily configure these headers to protect against common attacks. Key headers include: |
||||
|
||||
- **Content Security Policy (CSP):** Controls resources the browser can load. |
||||
- **Strict-Transport-Security (HSTS):** Enforces HTTPS connections. |
||||
- **X-Frame-Options:** Prevents clickjacking attacks. |
||||
- **X-XSS-Protection:** Enables XSS filtering in browsers. |
||||
- **Referrer-Policy:** Controls referrer information sent with requests. |
||||
|
||||
Cloudflare simplifies setting these headers, improving website security with minimal effort. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Configure HTTP Headers - Cloudflare](https://developers.cloudflare.com/fundamentals/reference/http-headers/) |
||||
- [@article@Quick Reference to Security Headers](https://web.dev/articles/security-headers) |
||||
@ -1 +1,7 @@ |
||||
# Webhook Handling |
||||
# Webhook Handling |
||||
|
||||
Cloudflare can handle webhooks to trigger actions based on external events. You can configure Cloudflare Workers to receive webhook requests and process the data. This allows you to integrate Cloudflare with other services like GitHub, Slack, or monitoring tools. When an event occurs in the external service, it sends a webhook to your Cloudflare Worker, which can then perform actions such as updating DNS records, purging the cache, or sending notifications. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Configure Webhooks - Cloudflare](https://developers.cloudflare.com/notifications/get-started/configure-webhooks/) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Workers AI |
||||
# Workers AI |
||||
|
||||
Cloudflare Workers AI allows you to run AI inference directly on Cloudflare's global network, close to your users. This eliminates the need to send data to centralized AI servers, reducing latency and improving performance for AI-powered applications. You can use Workers AI to perform tasks like image recognition, natural language processing, and sentiment analysis at the edge. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Workers AI - Cloudflare Docs](https://developers.cloudflare.com/workers-ai/) |
||||
- [@official@Models · Cloudflare Workers AI](https://developers.cloudflare.com/workers-ai/models/) |
||||
@ -1 +1,9 @@ |
||||
# Workers Lifecycle |
||||
# Workers Lifecycle |
||||
|
||||
A Cloudflare Worker's lifecycle is short and stateless. Each invocation starts when a request hits the Cloudflare edge. The Worker executes its code to handle the request. Once the response is sent (or an error occurs), the Worker instance terminates. There's no persistent state between requests unless you use services like KV or Durable Objects. This stateless nature ensures scalability and quick response times. Understanding this lifecycle is crucial for designing efficient Workers that can handle a high volume of requests. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Workers RPC - Lifecycle](https://developers.cloudflare.com/workers/runtime-apis/rpc/lifecycle/) |
||||
- [@official@How Workers Works · Cloudflare](https://developers.cloudflare.com/workers/reference/how-workers-works/) |
||||
- [@official@Introducing workerd: the Open Source Workers Runtime](https://blog.cloudflare.com/workerd-open-source-workers-runtime/) |
||||
@ -1 +1,8 @@ |
||||
# Workers Runtime Environment |
||||
# Workers Runtime Environment |
||||
|
||||
The Workers runtime environment is a lightweight JavaScript execution environment running on Cloudflare's edge network. It's based on V8, the same engine that powers Chrome and Node.js, but optimized for speed and security. Workers have limited access to global variables and APIs compared to a traditional Node.js environment, focusing on handling HTTP requests and responses. It provides APIs for caching, KV storage, and accessing request information, enabling performant and globally distributed serverless functions. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@How Workers Works · Cloudflare](https://developers.cloudflare.com/workers/reference/how-workers-works/) |
||||
- [@official@Introducing workerd: the Open Source Workers Runtime](https://blog.cloudflare.com/workerd-open-source-workers-runtime/) |
||||
@ -1 +1,8 @@ |
||||
# Workers Security Model |
||||
# Workers Security Model |
||||
|
||||
Cloudflare Workers operate within a secure, isolated environment. The Workers runtime enforces strict security boundaries, preventing Workers from accessing sensitive data or interfering with other processes. Workers have limited access to the outside world and must explicitly request resources. Cloudflare's global network provides inherent DDoS protection and mitigates common web vulnerabilities. This secure execution environment ensures that Workers can safely process requests without compromising the overall security of the platform. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Security Model · Cloudflare](https://developers.cloudflare.com/workers/reference/security-model/) |
||||
- [@official@Workers RPC — Visibility and Security Model - Cloudflare Docs](https://developers.cloudflare.com/workers/runtime-apis/rpc/visibility/) |
||||
@ -1 +1,8 @@ |
||||
# Workflows |
||||
# Workflows |
||||
|
||||
Cloudflare Workflow allows you to automate tasks and orchestrate different Cloudflare services through a visual, no-code/low-code interface. You can create workflows that trigger based on various events (e.g., HTTP requests, scheduled triggers) and perform actions such as modifying HTTP headers, routing traffic, or integrating with external APIs. It's designed to simplify complex configurations and automate repetitive tasks without requiring extensive coding knowledge. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Cloudflare Workflows · Cloudflare](https://developers.cloudflare.com/workflows/) |
||||
- [@opensource@Cloudflare Workflows Starter](https://github.com/cloudflare/workflows-starter) |
||||
@ -1 +1,16 @@ |
||||
# Wrangler |
||||
# Wrangler |
||||
|
||||
`Wrangler` is the command-line interface (CLI) for Cloudflare Workers. It simplifies the process of developing, testing, and deploying Workers. With `wrangler`, you can: |
||||
|
||||
- Create new Worker projects. |
||||
- Develop Workers locally. |
||||
- Deploy Workers to Cloudflare. |
||||
- Manage secrets and environment variables. |
||||
- Configure bindings to other Cloudflare services. |
||||
|
||||
`Wrangler` streamlines the entire Workers workflow, making it an essential tool for any Cloudflare Workers developer. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Wrangler Documentation](https://developers.cloudflare.com/workers/wrangler/) |
||||
- [@official@Wrangler Commands](https://developers.cloudflare.com/workers/wrangler/commands//) |
||||
|
||||
@ -1 +1,8 @@ |
||||
# Wrangler |
||||
# Wrangler |
||||
|
||||
Wrangler is the command-line interface (CLI) tool for building, deploying, and managing Cloudflare Workers. It simplifies the development workflow by providing commands for creating new projects, testing Workers locally, deploying code to Cloudflare's edge network, and managing secrets. Wrangler automates many tasks, making it easier to develop and deploy serverless applications on Cloudflare. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Wrangler Documentation](https://developers.cloudflare.com/workers/wrangler/) |
||||
- [@official@Wrangler Commands](https://developers.cloudflare.com/workers/wrangler/commands//) |
||||
|
||||
Loading…
Reference in new issue