In this case they're being tweaked so that you never worry about your next app taking over the world and dealing with billions of requests per day.

Please

@rauchg

don't forget the Apollo community :D I know you guys have a lot to handle right now, but we were super excited to host everything on now. I hope with get more details on this new approach on the coming weeks

It's really not a bad tradeoff to make, all things considered.

@zouhair

I meant it when I wrote in the blog post that my main priority is to address all the customer workloads perfectly.

I also wouldn't be calling this 2.0 if we had to reject entire classes of interesting applications.

Also, everyone is free and welcome to email me directly at rauchg@zeit.co

And I'm happy to jump on a call with any teams that need further reassurance.

I am sorry. I must be missing something. What does this mean exactly? "00% confident that this is the right direction for the platform"? Does this mean you do not believe that docker is a good tool for production deployments? The only alternative interpretation I can make, is that the Zeit Now platform has many more non-docker than docker deployments, and then, it makes sense from Now's perspective, but it also means a "hard goodbye" to anyone seeking docker builds.

@rauchg

what is your approach to "address all the customer workloads perfectly"? Is there a place we can submit use-cases that don't have an apparent fit for 2.0?

@Matt

we are aware of several of them, please let me know if I forgot any:

- GraphQL servers like Apollo Server

- WebSocket subscriptions

- Control loops (e.g.: tailing a cursor from a database)

- Cron jobs

All of these will be addressed, and others as well!

@rauchg

Can we still create an entire application on now 1.0 and choose a 1.0 plan? I definitely can't use 2.0 in it's current state.

@rauchg

I think , the now.json should accept all versions. It will make all of us happy !

What about elasticsearch?

@revskill

it does

@akryum

that was never possible to host to begin with, we only ever supported non-durable workloads

But we definitely want to make it super easy to connect and set up elasticsearch clusters

That's a big use-case we are looking into.

@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.