When not to use Deno ☄️

1

Supabase

Database reads are expensive and slow. There's a multitude of other reasons why caching is essential, but for the project I'm working on I'm using supabase and their free tier supports only a limited amount of bandwidth. To avoid any rate-limiting I added a Redis layer in front of it to reduce the number of queries that hit the database directly.

#Developer Tools #Realtime Backend / API #Backend As A Service 426 social mentions

2

Redis

Database reads are expensive and slow. There's a multitude of other reasons why caching is essential, but for the project I'm working on I'm using supabase and their free tier supports only a limited amount of bandwidth. To avoid any rate-limiting I added a Redis layer in front of it to reduce the number of queries that hit the database directly.

#Key-Value Database #NoSQL Databases #Databases 183 social mentions

3

ExpressJS

Though any traditional server environment will enable this, I used Node as it's close to Deno and simple to use. With a few lines of code, an express server that creates a single client on start will enable any incoming request to reuse the same connection. Adding some simple routing to detect request params and respond with what Redis returns then lets allows the cache requests in Deno to be swapped with GET requests to this server.

#JavaScript Framework #Node.js Framework #Web Frameworks 423 social mentions

4

Deno

Import { connect } from "https://deno.land/x/redis/mod.ts"; Const redis = await connect({ hostname, port }); Let cachedResult = await redis.get(query); Let result = cachedResult; If (!cachedResult) { result = db.get(query); await redis.set(query, result); } Return result;.

#Typescript #JavaScript #Web Development Tools 195 social mentions