4 ms·
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
by rymate1234 7y ago
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-js-server-now-node-server/ https://zeit.co/docs/v2/deployments/official-builders/node-j...
- bobfunk 7y agoYou can do the same with Netlify functions. Here's an example: https://github.com/netlify-labs/netlify-functions-express https://github.com/netlify-labs/netlify-functions-express
- rymate1234 7y agoThat 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/aws-serverless-express 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 https://zeit.co/docs/v2/deployments/builders/overview
- bobfunk 7y agoYou 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!