libaws VS deno

i print the error along with file and line number every time i return it. clunky, but it works.

in fact i print file and line with every log message.

https://github.com/nathants/libaws/blob/87fb45b4cae20abd1bb1...

cloud is so good now it’s hard to justify not doing something bespoke. ec2 spot is insanely cheaper than turnkey cicd, and better in almost every way.

i’m delighted to pay 30% over infra cost for convenience, but not 500%. and it better actually be convenient, not just have a good landing page and sales team.

this month i learned localzones have even better spot prices. losangeles-1 is half the spot price of us-west-2.

for a runner, do something like this, but react to an http call instead of a s3 put[1].

for a web ui do something like this[2].

s3, lambda, and ec2 spot are a perfect fit for cicd and a lot more.

1. https://github.com/nathants/libaws/tree/91b1c27fc947e067ed46...

2. https://github.com/nathants/aws-exec/tree/e68769126b5aae0e35...

like linux, cloud is a lot to learn, but worth it.

like linux, cloud is best kept simple, or it can become brittle and confusing.

like linux, cloud has a lot of cool things like zfs, that should be appreciated but rarely used.

like linux, using go makes your life a lot easier. the aws go sdk is the documentation.

like linux, you have to learn a lot and then find the core utility you actually care about. for me it is:

https://github.com/nathants/libaws

the good new is, for the 95% of projects that can tolerate it, aws the good parts are actually both simple and easy[1].

it’s hard to find things you can’t build on s3, dynamo, lambda, and ec2.

if either compliance or a 5% project demand it, complicated solutions should be explored.

1. https://github.com/nathants/libaws

i also wanted a good cli for aws, and built one:

https://github.com/nathants/libaws

companies like fly are fantastic.

they provide a good service, and they put market pressure on aws.

cool transition and fun writeup!

for low, intermittent traffic sites, go on lambda might be a better comparison:

https://github.com/nathants/libaws/tree/master/examples/simp...

lambda + s3. add ec2 spot if you need it.

just make sure you understand how billing works. mostly it’s just egress bandwidth is expensive.

do something like this:

https://github.com/nathants/aws-gocljs

or with less opinions:

https://github.com/nathants/libaws/tree/master/examples/simp...

welcome to cloud, glhf!

aws ux for retaining both hair and sanity.

https://github.com/nathants/libaws

build and scale systems with artificial load on aws! scaling the load testing will be just as interesting as scaling the system under test.

start with low bottlenecks, ie a cluster of c6i.large ec2 spot. how fast can you do this? have fast can you scale that? ec2 and s3 is all you need to build anything.

use ec2 spot, avoid network egress, avoid cross region/zone traffic, create and destroy ec2 instances as needed instead of letting them sit idle. you could grow system scaling intution for the price of your streaming subscriptions.

start with something like this:

https://github.com/nathants/libaws/tree/master/examples/comp...

maybe mess around with public datasets on aws, just make sure to be in the correct region to avoid data egress.

welcome systems friend. one accurate measurement is worth a thousand expert opinions. scaling is fun!

aws has too many knobs, presumably to satisfy the union of the needs of all the enterprise customers. that said, lambda+s3+dynamodb+ec2 are pretty good once you tape over all the knobs that aren't needed. i work with them like this[1].

these days i build on aws and r2. aws for the nuts and bolts, r2 for high bandwidth egress. it's a perfect match.

1. https://github.com/nathants/libaws

NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.

https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

QUIC is very exciting, after seeing what it can do for performance in Cloudflare network and Cloudflare workers, I can't wait to finally see it in Deno[0] 1.41.

[0] https://github.com/denoland/deno/pull/21942#issuecomment-192...

So as an end user it's kind of like https://deno.com/ where you buy into a runtime + comes prepacked with DBs (k/v stores), scheduling, and deploy stuff?

> by storing Unison code in a database, keyed by the hash of that code, we gain a perfect incremental compilation cache which is shared among all developers of a project. This is an absolutely WILD feature, but it's fantastic and hard to go back once you've experienced it. I am basically never waiting around for my code to compile - once code has been parsed and typechecked once, by anyone, it's not touched again until it's changed.

Interesting. Whats it like upgrading and managing dependencies in that code? I'd assume it gets more complex when it's not just the Union system but 3rd party plugins (stuff interacting with the OS or other libs).

~90MB+ at this stage and do now allow compression without erroring out. Deploying ala Golang is not feasible at that level but could well be down the line if this dev branch is picked up again!

The exe output grew from from ~50MB to plus ~90MB from 2021 to 2024: https://github.com/denoland/deno/discussions/9811 which mean Deno is worse than Node.js's pkg solution by a decent margin.

Behind the scenes is a simple Sveltekit-powered server function to fetch a Spotify client token then find a user's recommendation playlist and its track information. A Deno edge function to performs this data fetch and renders server-side Svelte.

If your application is written in JavaScript, integrating it with JavaScript extensions is a no-brainer. However, Secutils.dev is entirely written in Rust. How would I even begin? Fortunately, I recently came across an excellent blog post series explaining how to implement your JavaScript runtime in a Rust application with Deno: