deploy_feedback VS deno-lambda

That means we don’t need to transpile the Typescript code to ESM or CJS. Currently, only Deno Deploy can run your Typescript function out of the box. However, in order to keep the code small, we still need some sort of bundling. Luckily, Bun is also a bundler 😉

The online version of DocTrack is hosted through Deno Deploy and is accessible here.

One of the biggest annoyances with Deno deploy/functions is that there is no way to store any data. This would be very useful to e.g. cache an auth token, store a key/value pair, etc. See also: https://github.com/denoland/deploy_feedback/issues/110

Is any work being done to fix this? Or is this out of scope currently?

This can definitely be used as an alternative to Workers if you wanted to self-host.

You could also use Deno Deploy (https://deno.com/deploy), if you wanted to use a Workers alternative but don't want to self-host

One of the valuable features of Solid Start is that you can use so-called "adapters" to completely change the output into something deployable basically everywhere that serves pages and with quite a lot of options: there are adapters for amazon web services, cloudflare pages and workers, deno deploy, netlify, standard node server (the default), vercel, and static deployment - the latter allows us to build something that we can put on github pages.

Developed using Fresh framework (https://fresh.deno.dev) and deployed to Deno Deploy (https://deno.com/deploy). For persistent storage I use a simple MySQL instance from DigitalOcean.

I've been really enjoying Deno for personal projects! The developer experience is excellent and Deno Deploy makes it easy to quickly & easily get things deployed.

I really liked the ease of https://fresh.deno.dev/ and https://deno.com/deploy. Just went through the getting started guide and it was basically 'run these two commands and log in here'. But I already know react, so if that's an issue maybe choose something else.

Like CDN, edge networks are supposed to be deployed at a large scale and shared among many tenants. This requires isolated execution contexts (so data can't leak between tenants) with a tiny footprint (so contexts can be frequently created and disposed of without hurting performance). NodeJS is too bloated to be a viable solution. Slimmer Javascript runtimes, like Next.js's edge runtime, Cloudflare's workerd, Deno deploy, and bun, are created to fulfill this specialized job.

Using Deno with AWS Lambda functions requires a custom runtime. You can build your own runtime or use one that already exists. If you’re concerned about security, I suggest maintaining a copy of an existing runtime and carefully inspecting updates or creating your own runtime. For this proof of concept, I deployed the Serverless Application Repository (SAR) app for Deno into my AWS account. I used the included Lambda layer and the provided.al2 Lambda runtime to create my Deno Lambda function. I created a file called index.ts with some basic JavaScript code that makes requests to two different websites and returns the HTTP status code of the response or a caught error. I then updated the function’s configuration to reference the exported handler function.

I'm doing a simple PoC / testing with Deno using https://github.com/hayd/deno-lambda and specifically the CDK instructions.

As I had mentioned, it requires using a Lambda Layer. See: https://github.com/hayd/deno-lambda/blob/2d90756a0f18b57f16e...

Using your own image (i.e. without using the base AWS image with the layer) you'd get even worse cold start times.

Decorators and TypeScript aren't supported out of the box in Lambda (without using deno) so we'll also need a transpilation step if we go this route. Fortunately this is a mostly solved problem for AWS CDK, AWS SAM and Serverless Framework users. If you want or need to roll your own, esbuild is a great place to start and seems to be the bundler of choice for this purpose.

In addition to the stuff posted here, there's the deno-lambda project for deploying to AWS Lambda

Cloud hosting support. Deno runs fine in a container, but lambda/cloud function support is difficult on most providers. deno-lambda exists but it only applies to AWS and can't be used with all CICD tools. Deno Deploy also exists but it's pretty new.