Live data from Hacker News

Deno raises $21M

deno.com

161–170 of 397 posts

Re: Deno raises $21M

#161

As a Deno fan I was surprised to learn that the free tier for Deno Deploy includes 100k requests per day and 100GB of bandwidth monthly. I know I'll be trying it out now.

> Up to 10ms CPU time per request

So less than 17 minutes of CPU time per day - not a lot, but also not nothing.. But at 10ms per request, what would one use it for? Just server-side rendering for something simple?

Re: Deno raises $21M

#162
post #27

Earlier quoted context omitted.

> are there real-world, commercial products actually running on """serverless""" architecture? Yeah, thousands I would imagine. The last two companies I have worked at have been 100% serverless or nearly 100%. > no matter how much I think about that whole concept, I see no application for it that couldn't be done better, faster and easier with regular tools Considering you have to ask if there are _any_ products runn…

what was the product and the scale then?

I'd rather not list my last two companies or their scale, but I can assure you they are real companies that exist, have users, and make money. I'm not sure why I even would be asked to.

Re: Deno raises $21M

#163

Earlier quoted context omitted.

No, Netlify actually uses Deno to some degree: https://www.netlify.com/blog/announcing-serverless-compute-w...

Right, but the $21M of funding seems to be for Deno Deploy, the product, not Deno, the CLI.

The wording in that blogpost might be a bit off, here it is more in-depth: https://deno.com/blog/netlify-edge-functions-on-deno-deploy

Netlify is using Deploy

Re: Deno raises $21M

#164
post #130

Earlier quoted context omitted.

https://deno.com/deploy/pricing is their business model. They charge you for CPU and bandwidth more than they pay for it.

Right, my point is that any number of cloud providers could swoop in and offer the same product for probably cheaper

This is generally true about every company though. Someone can always swoop in, and huge incumbents can always do it cheaper, at least in theory.

Re: Deno raises $21M

#165
post #27

Earlier quoted context omitted.

> are there real-world, commercial products actually running on """serverless""" architecture? Yeah, thousands I would imagine. The last two companies I have worked at have been 100% serverless or nearly 100%. > no matter how much I think about that whole concept, I see no application for it that couldn't be done better, faster and easier with regular tools Considering you have to ask if there are _any_ products runn…

> Yeah, thousands I would imagine. The last two companies I have worked at have been 100% serverless or nearly 100%. If you can answer (for legal or other reasons you might not be able to): What kind of monthly bills did your setup have and how many req/s did you serve (in lack of a better metric)? It'd also be useful to know average min/max response time if that's something you remember. I wish that was a good way o…

I can't list that, but both companies migrated to serverless and both companies are glad they did.

There is more than "raw dollar amount on monthly bill" to account for in cost, as well. For one, there's stability and the toll that takes on both your team and your customers. Not saying non-serverless apps are not stable by nature, but I've now been part of two teams that have seen the same types of benefits and those benefits line up with the "sales pitch" benefits.

Re: Deno raises $21M

#166

As a Deno fan I was surprised to learn that the free tier for Deno Deploy includes 100k requests per day and 100GB of bandwidth monthly. I know I'll be trying it out now.

> Up to 10ms CPU time per request So less than 17 minutes of CPU time per day - not a lot, but also not nothing.. But at 10ms per request, what would one use it for? Just server-side rendering for something simple?

proper applications as well. example is the https://deno.land website has an average CPU time of 6ms. CPU time means it doesnt include any IO bound operations, so ie doing a fetch request wont really contribute to the CPU time.

Re: Deno raises $21M

#167
post #69

This question is going to make me sound like a jerk, but why do you want to write your back-end in JS? Deno looks like a great improvement over node.js, but I don't feel compelled to use it. It seems like people jumped to node based on some performance promises that didn't really pay off (IMO). And since then, we have newer options like Rust, Go, and Elixir as performant back-end options, and even older choices like…

Sharing code with the browser can be really sweet. At a past job we used TypeScript, and I had whipped up some shared types that our API was forced to conform to, and that automatically generated a strongly typed API client for the frontend to use. Sure, you can do that with some other protocol or server like GraphQL/Hasura/writing up a JSON schema, but it was pretty sweet that A) any of our engineers could figure out how to make the endpoints they needed to implement a new feature, B) these types could generally be inferred from the actual API implementation without having to explicitly write types out which completely eliminated bugs around API misuse with minimal extra code, and C) all of the code we wrote followed the same linters, formatters, idioms, and utilities (fetching, logging, error handling, and so on). There are projects out now that wrap up a lot of what I had done like tRPC [1], as a testament to the value of the shared abstractions.

[1] https://trpc.io/

Re: Deno raises $21M

#168
post #69

This question is going to make me sound like a jerk, but why do you want to write your back-end in JS? Deno looks like a great improvement over node.js, but I don't feel compelled to use it. It seems like people jumped to node based on some performance promises that didn't really pay off (IMO). And since then, we have newer options like Rust, Go, and Elixir as performant back-end options, and even older choices like…

To me its very powerful to have the same developers do both front end and back end. With modern frameworks its probably easier for front end devs to do back end work than Rust/Go/Elixir devs to dirty themselves with JS. So even though ts is suboptimal it allows one language, one set of tools and developers.

Re: Deno raises $21M

#169
post #159

Quoted post unavailable.

Attack the technology all you want as those are some valid criticisms, but the sarcastic personal attack at the end seems unnecessary. Imagine how he'd feel reading that. Would you want to have that same feeling yourself?

Re: Deno raises $21M

#170
post #159

Quoted post unavailable.

> Even the source of node it’s just a bunch of function from pre-ES4

Old code does not mean bad code. Seems like a silly thing to look at, honestly.

A bunch of java was written pre-java8, does that make it all bad? No, no it doesnt.

Post reply on HN