@dannyben

Docker is a great implementation detail

That's awesome

Any example for it ? It looks awesome. Imagine it will allow us to incrementally refactor big monothlic to lambdas.

In fact, right now builders can choose from a whitelist of runtimes, but in the future there will be more and more flexibility there

What about subscribing to 1.0?

Just version: 1 will work! We mention this in the upgrade guide. That's also why all existing users have to actually go out of their way by specifying version: 2 to upgrade. We didn't want to hurt any existing use-cases.

What i mean is, using two versions in the same file.

@akryum

new subscriptions will also work with version: 1 in now.json until full compatibility is achieved.

@revskill

that's not possible currently, but you could use the path alias feature!

(Notice that the new model also dramatically simplifies the gateway aspect of things)

I have a majestic monothlic under graphql endpoint for both http and subscription to render a NextJS application. It'll be deployed under version 1. My plan is to moving all mutation to lambdas under v2. What the now.json should be in this case ?

@rauchg

Yes, I absolutely love the ability to use the filesystem itself instead of path aliases. Hosting all endpoints in a single source tree is killer DX

@rauchg

Do you have plans to support things like redis or rabbitmq for websocket subscriptions?

@revskill

that's a very great way to do an incremental migration. Good decision. What I would do is set up an alias for your new v2 monorepo (e.g.: v2.api.company.com), and then use path alias for your current production app to start progressively migrating paths.

@nathaniel

It's not even just the best possible DX. It builds faster. It's more secure, by isolating parts of the application from one another at execution time, but not in the source code organization.

@akryum

Now you are speaking my language. I think that's the true way to scale realtime communication.

For example, your stateless endpoints can populate a queue that gets consumed by a client over a websocket connection

So, you don't put all your eggs into one server basket, and you neatly separate responsibilities.

@rauchg

I'm not as concerned as others on this thread, as all my projects will work fine on the new platform. That being said, I literally just migrated earlier this week from 1.0 to the serverless docker "v2" beta :/ I agree that this looks like the future, but why the rush to get rid of serverless docker? It is still an amazing product, that has a massive competitive advantage over any other offering I've seen! Why not two concurrent offerings? Now Lamba & Now Container?

That what's I was gonna do, but if I can just use now API for this it's neat

@rauchg

I also loved merging the testing and build phase, and having that all triggered by a github push. It seems unclear how CI fits into this new paradigm. Is that something that would have to be triggered by the builder?

@rauchg

thanks a lot for commenting. current discussions aside I think that now is an amazing innovator and pretty much everything you guys released this far is pretty much ground breaking. I would love to hear your thoughts on the issue of vendor lock-in / app portability though - as a lot of the stuff that is coming is quite unique to Zeit / now. do You think certain elements of zeits stack could become a standard outside of now?

So I guess I'll just develop on Now 1.0 and wait & see if Now 2.0 will work.

@nathaniel

the "rush" is in the interest of truth-seeking. We, and I, learned a tremendous lot from that beta. I learned what works and what doesn't. I truly think this new world shouldn't wait and our customers will benefit immensely from it.

I think these systems are all in competition to one another to a very large extent, and I think this is the winner.