Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno Queues

deno.com

Post reply on HN
Print view View original

51–60 of 168 posts

Re: Deno Queues

#51

Post by domh »

paxys wrote: post #31
herpdyderp wrote: post #27

Earlier quoted context omitted.

Deno is compatible with web code to a much deeper level than Node.js is. As the Deno website puts it: "Built with web standard APIs". This might not make a difference to most. Personally though, as someone who strives really hard to share code between frontend and backend, I'm excited for it. This is pretty much the only reason I see Deno eventually winning out over Node.js (in the long run). I don't have the time to…

The single piece of extra browser compatibility I have found in Deno is that it supports the fetch API, and Node 18+ has that as well. Beyond that there is really no difference between the two.

Whilst I mostly agree, and Node has arguably been forced down the browser-compatible route (for stuff like fetch() and web streams). There is a bunch of other stuff that isn't in Node, or it has it's own APIs for... alert/confirm for getting user input, Web Crypto, URLPattern etc. You can see them all here: https://docs.deno.com/runtime/manual/runtime/web_platform_ap...

Re: Deno Queues

#52

Post by EGreg »

Isn't deno running locally no your self-hosted instance? How are they charging?

  Enqueuing a Message: Each enqueue action translates into a KV write operation.

  Receiving a Message: Every received message entails a KV write, and a single request charge.
I would be really curious to know. Are they only talking about Deno Deploy in the cloud, with FoundationDB? Is this "open core"?

Re: Deno Queues

#53

Post by marmaduke »

lopatin wrote: post #17

> Leveraging public cloud infrastructure has traditionally demanded sifting through layers of boilerplate code and intricate configurations, often monopolizing a significant chunk of the developer’s time and energy. I don't buy this line of reasoning. At the end of the day we are building infrastructure that needs to be reliable. Spending 30 minutes to set up an SQS queue (proven technology) doesn't sound as bad as p…

I don't recall SQS taking anytime to set up queues, at least when using Celery (python task queue). IIRC you just name it in your code and use it.

Re: Deno Queues

#54

Post by ecnahc515 »

zoogeny wrote: post #36

I think what Deno is aiming for here is actually very forward thinking. I'm using Go for the first time this year and some aspects of the language are very C like. Of the list of things that isn't C like (e.g. GC allowing one to return what look like stack allocated pointers from functions) there is the obvious inclusion of things like `map[string]string`. I bring this up because it struck me that inventing a languag…

> e.g. GC allowing one to return what look like stack allocated pointers from functions

I think this is due to having escape analysis and SSA rather than having a GC.

Re: Deno Queues

#55

Post by brundolf »

> Leveraging public cloud infrastructure has traditionally demanded sifting through layers of boilerplate code and intricate configurations, often monopolizing a significant chunk of the developer’s time and energy. Our goal is to distill these intricacies into user-friendly primitives, enabling developers to design, refine, and launch their projects with unmatched speed.

I really like this

Re: Deno Queues

#56

Post by math_dandy »

Under the hood, does DenoKV implement an abstraction that specializes locally to SQLite and to Deno Deploy in the cloud? Or are DenoKV local and DenoKV cloud two separate products with a common public API?

Re: Deno Queues

#58

Post by rahkiin »

ranting-moth wrote: post #57

Pricing? I thought Deno was some sort of node.js replacement. What am I missing and can I use this either locally and/or self hosted without paying for it?

The article says development (locally) it uses SQLite. On deployment to Deno it is part of their cloud offering

Re: Deno Queues

#59

Post by simonw »

ranting-moth wrote: post #57

Pricing? I thought Deno was some sort of node.js replacement. What am I missing and can I use this either locally and/or self hosted without paying for it?

This is the same trick as the rest of Deno KV: the open source version uses SQLite, but when you deploy to their cloud product you get Foundation DB (proprietary) instead:

> Since Queues are built on Deno KV, it uses SQLite when running locally and FoundationDB when running on Deno Deploy for maximum availability and throughput.

I wrote a bit more about this pattern here: https://til.simonwillison.net/deno/deno-kv

Re: Deno Queues

#60

Post by vorticalbox »

math_dandy wrote: post #56

Under the hood, does DenoKV implement an abstraction that specializes locally to SQLite and to Deno Deploy in the cloud? Or are DenoKV local and DenoKV cloud two separate products with a common public API?

Code was the api is the same.

When you use it locally the database is only on your device however all deno processes can access the same dB so you can use it to pass data around just like you can for localStorage that deno also supports.

When you use it in the cloud (deno deploy) then saves are replicated across regions.

Deploy is server less.

KV is simply a wrapper around sqlite with that you get atomic transactions that you wouldn't with local storage

Post reply on HN