พร็อกซีฐานข้อมูลด้วย Deno

Welcome to our lesson on Deno database proxies! An edge database proxy acts as an intermediary layer between your application (like a Cloudflare Worker) and your database.

Instead of your edge function connecting directly to the database, it talks to the proxy. The proxy then handles the actual database connection.

• Why use them? They centralize connection management, enhance security, and enable data transformation before reaching your database.

Deno is an excellent choice for building these database proxies at the edge. Here's why:

• Native HTTP Server: Deno has a powerful, built-in web server, perfect for handling proxy requests.
• Security Model: Its granular permission system means you explicitly grant network or file access, enhancing security.
• Performance: Deno's fast startup times and efficient runtime make it suitable for responsive proxy services.
• TypeScript First: Built-in TypeScript support helps you write more robust and maintainable code for your proxy logic.

Let's start by creating a basic Deno HTTP server. This server will listen for incoming requests and respond with a simple message, acting as the foundation for our proxy.

Try running this example:

Now, let's modify our Deno proxy to forward incoming requests to a 'mock' database endpoint. In a real scenario, this would be your actual database API or a service that interacts with it.

Here, we use a public JSONPlaceholder API to simulate a database call.

Database connections are expensive to establish. Serverless functions, like Cloudflare Workers, are often short-lived and stateless. If each Worker instance opens a new connection, you can quickly exhaust database connection limits.

Connection pooling is a technique where a pool of open, reusable database connections is maintained. When a request comes in, a connection is borrowed from the pool instead of creating a new one.

A Deno database proxy can effectively manage connection pooling. Unlike ephemeral Workers, a Deno proxy (e.g., deployed on Deno Deploy or a persistent server) can be a long-lived process.

This allows it to maintain and manage a pool of database connections, serving multiple requests from various Workers without constantly opening and closing connections. This significantly reduces overhead and improves database performance and stability.

Security is paramount. Your Deno proxy acts as a gateway to your database, so it must be secured:

• Hide Credentials: Never expose raw database credentials in your Worker code. The proxy should store and use these securely.
• Authentication for Proxy: Implement authentication (e.g., API keys, JWTs) for your Workers to access the proxy itself. This ensures only authorized edge functions can send requests.
• Permissions: Deno's explicit permission model helps. Only grant the proxy network access to your database, not arbitrary internet access.

Beyond just forwarding, a Deno proxy can transform data. This means modifying request bodies before sending them to the database or altering responses before returning them to the Worker.

This is useful for adding metadata, filtering sensitive information, or normalizing data formats.

How would a Cloudflare Worker interact with this Deno proxy?

The Worker would simply make a standard HTTP fetch request to the Deno proxy's endpoint. If your Deno proxy is deployed on a platform like Deno Deploy, it will have a public URL.

The Worker sends its request, the Deno proxy processes it (e.g., handles pooling, adds security, transforms data), and then forwards it to the actual database, returning the database's response to the Worker.

Which of the following are benefits of using a Deno-based database proxy at the edge?

In this lesson, we explored how to create efficient database proxies using Deno. We learned that Deno's native HTTP server and security model make it ideal for this task.

• We built a basic proxy that forwards requests.
• Understood the importance of connection pooling and the proxy's role in it.
• Discussed securing your proxy and transforming data at the edge.
• Finally, we saw how Cloudflare Workers can interact with such a proxy.

This pattern provides a powerful way to manage database interactions from your edge applications.