[pcr910303]

I instantly thought of the incomplete/error prone Zeit Now dev that was introduced a few weeks ago. If this(Netlify Dev) can replicate the entire system stably I might move on to Netlify Edge. Replicating and testing is a pretty big deal :-)

Offtopic, but can anyone explain the differences between Zeit Now v2 and Netlify Edge?

[evanweaver]

Netlify Dev also includes support for accessing FaunaDB GraphQL Cloud, launched in beta today (https://fauna.com/blog/getting-started-with-graphql-part-1-i...).

We are working on adding support for a 100% local development workflow in Netlify Dev. It would be lovely to know what you think is missing from stateful local workflows in both Zeit and Netlify.

[rymate1234]

As far as I'm aware, zeit now can run server side code whereas netlify edge can only do at most some serverless functions, and is otherwise focused entirely on serving the front end

[icebraining]

Zeit Now also seems to target serverless functions, not stateful applications.

[rymate1234]

Yeah but with Zeit Now the serverless functions can actually serve the application, so if you need SSR with dynamic data you're able to, whereas with netlify it's static html being served with optional AWS style lambda functions.

For instance Zeit can host a standard node server to serve your application if necessary https://zeit.co/docs/v2/deployments/official-builders/node-j...

[bobfunk]

You can do the same with Netlify functions. Here's an example:

https://github.com/netlify-labs/netlify-functions-express

[rymate1234]

That example doesn't serve the main website, like all netlify functions they can only handle requests under the .netlify route for functions https://express-via-functions.netlify.com/.netlify/functions...

Whereas on Zeit Now the root of the website can be a web server written in multiple languages, and offer the ability to make your own "Lambda Builder" if necessary https://zeit.co/docs/v2/deployments/builders/overview

[bobfunk]

You can rewrite URLs to serve the main website as well. We're generally bullish on but DJing server side rendering, but a rule like this totally works:

/* /.netlify/functions/app/:splat 200!

[k__]

Yes, I have the feeling the whole "replicate locally" goes in the wrong direction.

You're just lying to yourself when saying local is the same as cloud...

[sudhirj]

If your cloud edge functions only (completely stateless functions or containers run without any directly attached data stores) then you can pretty reliably simulate it locally - you can configure your own dev machine as an edge node.

Stuff like Lambda@Edge, Cloudflare Workers etc all have very strictly defined APIs that are executed on V8 (modified for security, but not enough to be incompatible). If you run a pure function on your local machine you can be pretty sure it’ll run on the edge.

We’ve already done this quite well with Docker - the image you run locally is cryptographically the same binary bytes you’ll run on production. It’s not that surprising to see it for edge functions.

[k__]

Sure if you doing unit-tests/one function that works.

But as far as I know, unit tests aren't the place to be in terms of serverless testing.

Integration and E2E tests are much more important and that's where the whole "run locally" stuff breaks down rather quickly.

[icebraining]

Why? They're just computers, what makes your local machine that different from a Netlify server?

[k__]

Because functions are small self-contained stateless bits of code, they don't need much testing by themselves.

You need to test them with the services they are using and replicating your whole cloud infrastructure locally is nearly impossible.

[icebraining]

Maybe they'll tell me I'm wrong, but Netlify strikes me as not targeting people who need a "whole cloud infrastructure" (since they don't offer many services), but a static site with a few simple backend functions.

[k__]

Cloud be, yes.