HNHacker News
TopNewBestAskShowJobs

Rauchg

3,589 karma · joined December 8, 2009

Guillermo Rauch. https://twitter.com/rauchg https://vercel.com
submissionscomments
Rauchg··on Ncc: Node.js Compiler Collection
Ncc handles bundling `node_modules`. Your suggestion also introduces problems by not respecting commonjs module boundaries. (They’re akin to function scopes)
Rauchg··on Ncc: Node.js Compiler Collection
It’s definitely possible to extract some internals as plugins, but not all currently.

It would make more sense as a collection of plugins, and perhaps exposed as a preset.

But the intent is to precisely remove the extra setup, when all you need to do is publish your Node.js codebase as a single file.

Rauchg··on Ncc: Node.js Compiler Collection
The goal is to provide the experience that many other languages have, where you don’t configure anything. You just run “$tool build”
Rauchg··on Ncc: Node.js Compiler Collection
The goal is precisely to not just bundle, but incorporate important optimizations like the V8 Compile Cache (https://github.com/zeit/ncc/issues/51), which is what inspired the project and name to begin with.
Rauchg··on Now 2.0
What the parent comment is correctly saying is that for certain databases (that are oriented around stateful connections) you might benefit from a infrastructure-level optimization.

However, this is not the case for all databases. Furthermore, modern database vendors are extremely motivated to address the serverless usecase

Rauchg··on Now 2.0
Please keep in mind v1 will be around. We'll compel you to move by thoroughly reaching feature and use-case parity :)
Rauchg··on Now 2.0
We definitely look forward to giving you tools here. One can conceive a `now dev` process that faithfully reproduces the cloud gateway.
Rauchg··on Now 2.0
You'll find that nothing could bring us closer to this vision than making compute so remarkably inexpensive and scalable, out of the box, for everyone :) This is why serverless is so exciting to us.
Rauchg··on Now 2.0
This is something that is only necessary for legacy databases. Modern database providers give you gateways that deal with a huge number of connections with no issues.
Rauchg··on Now 2.0
Very important: you absolutely don't have to switch to or configure any cloud provider.

However, it is a very healthy thing to understand the "behind the scenes" in case you need to interoperate with existing APIs or databases[1]

[1] https://zeit.co/docs/v2/platform/regions-and-providers

Rauchg··on Now 2.0
To be perfectly clear: Now 2.0 is already fully rolled out to all regions.

As a matter of fact, this is an example of executing `now --regions all` :)

https://twitter.com/rauchg/status/1060616737215795200

Rauchg··on Now 2.0
Servers will also eventually go cold, unless you pay for them 24x7.

With the Now 2.0 design, you instead are very likely to not suffer from cold instantiation to begin with, due to the healthy constraints imposed by the system.

In other words, instead of ignoring cold boots, you just want to embrace them and make them minimal to begin with.

Rauchg··on Now 2.0
We are planning to give you very simple hooks and integrations to support WebSockets (e.g.: PubNub or Pusher).

For scalability reasons, it's likely you'll want to separate the code that deals with the "request-response" lifecycle from the realtime subscription.

Rauchg··on Now 2.0
The data can be stored anywhere. Now is only in charge of executing your code in the best infrastructure provider available.

It completely takes away the pain-points of setting up and managing the cloud infrastructure directly.

Rauchg··on Now 2.0
As far as we are aware, no one until today had solved the problem of compiling to serverless functions.

If you look at the solutions out there, they all involve you dealing with low-level APIs or config that have little to do with how you write most apps and frameworks in mainstream programming languages.

Rauchg··on Now 2.0
Logging is built-in. Just append /_logs to your deployment URL and you'll see all stdout and stderr of your underlying functions.
Rauchg··on Now 2.0
We are quite confident that 2.0 can meet all the customer needs of 1.0, but going far beyond in terms of scalability, at a much lower cost.

A great example of this is "doing work in a loop". Sure, you can spin up a process and try to schedule work yourself. At that point you're responsible for monitoring, and addressing all its failure modes.

In the 2.0 world-view, you can delegate a lot of the tough synchronization and scalability problems to the platform instead.

Rauchg··on Now 2.0
Keep in mind that the the intelligence that goes into the builders (which are OSS, which you can write your own of) is specifically around not making code changes.

Surely, some code changes are necessary to go serverless (when considering legacy servers and apps), but our goal is to always minimize that.

Rauchg··on Now 2.0
We have been running an internal beta of the jobs feature, and we'll keep everyone posted!

We agree that invoking entrypoints periodically is a much better way to model most worker / daemon workloads than a "stateful event loop".

The commitment to our customers is that we won't phase out V1 until this usecase (and others!) are thoroughly addressed.

Rauchg··on Now 2.0
Auto-generation is a great way to put it. Cloud functions are an incredible primitive, but in our view, they constitute primarily a compilation target.

Some small adjustments will be necessary when _importing_ large legacy codebases, but that's where using functions to also build your project comes in!

Rauchg··on Now 2.0
In our upgrade guide we detail how you can break down a "server" that you would otherwise deploy as a monolithic container:

https://zeit.co/docs/v2/platform/upgrade-to-2-0#don-t-rush-t...

The limits are there specifically to help in that transition, to avoid the problem described in the chart. They're a crucial learning extracted from the beta we ran.

Rauchg··on A quick way to browse GitHub issues and pull requests
Very cool!
Rauchg··on Docker cannot be downloaded without logging into Docker Store
On macOS, I recommend: `brew cask install docker`
Rauchg··on Faster – Fast key-value store from Microsoft Research
Haven't read the papers yet, but it immediately reminds me of Anna:

https://databeta.wordpress.com/2018/03/09/anna-kvs/

Rauchg··on Serverless Docker Beta
Thanks a lot for your feedback. I think adding playback controls on hover is going to help a lot.

We picked video/gif as the delivery format to give people a real-life impression of performance. (I took the videos myself while using the platform on a regular production plan.)

Rauchg··on Serverless Docker Beta
> Somehow this sounds very expensive to me (like restarting Windows 2000 every hour just to avoid a BSoD, except that here it’s not that time consuming a process)

The crucial difference is that the activation cost of booting up a full OS (like Windows 2000) is massive (typically involving a chain-reaction of CPU and IO-intensive init services), whereas that is not the case for our serverless infrastructure.

What you do point out is one of the most important engineering challenges we had to solve (and continue to be focused on).

Rauchg··on Serverless Docker Beta
This is not supported nor maintained by us. Thanks a lot for bringing it to our attention. We will do our best to reach out!
Rauchg··on Serverless Docker Beta
We will be announcing very clear pricing when it goes into GA. Needless to say, serverless makes for a much much cheaper (and robust) operation than VPS and traditional clusters.
Rauchg··on Serverless Docker Beta
As we mentioned in the blog post, there is zero difference between a `Dockerfile` you execute locally and one that you give to us.

[One of the differences is performance. You'll find that we can build and execute much more quickly :)]

There are many examples here: https://github.com/zeit/now-examples

Rauchg··on Serverless Docker Beta
Most databases are quite unfit for the serverless world that's becoming a reality, where the needs shift towards global replication, flexible horizontal scalability (sharding) and vertical (provisioned QPS).

We like and use CosmosDB because it fits this criteria. We anticipate that Google Spanner, CockroachDB and similar databases will become the go-tos in combination with ZEIT Now.

← PreviousPage 4 of 10Next →