menu
announcement

Spectrum is now read-only. Learn more about the decision in our official announcement.

ZEIT

Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

Channels
Team

clarify future support of docker on now platform

November 8, 2018 at 6:21pm
The ZEIT community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

clarify future support of docker on now platform

November 8, 2018 at 6:21pm
It seems zeit is moving away from allowing customers to utilize Docker as a common 'primitive'; would you kindly clarify this?
Show previous messages

November 9, 2018 at 7:02pm
I'm trying Azure Pipeline right now, the assistant auto detected my Dockerfile, got a green build with webpack build, docker build (nginx) and e2e tests without even looking at the doc (yet) still have to (auto) deploy it, but native dockerfile support is there, so far I had to do 0 modification to my application code
like-fill
2
NOTE: v1 is fully maintained and supported. We will only announce a deprecation date once we have ensured all our customers workloads are migrated and the tooling is in place for a smooth transition.
So v1 is destined to end at some point.
How about Apollo Stack with graphql subscription ? My realtime infrastructure is built on it. Even the escape hatch is Docker is soon abandoned here. So frustrated on NOW !
It would be really great if someone from the Zeit team could comment on this issue. reading through this thread there are several use cases that just don’t align well with the lambda model and even if now‘s stance is that this is the way forward it would only be fair to people in need of other use cases to bring clearity if now will be a viable option for them in the future.
Edited
I want to re-assure everyone that we are 100% confident that this is the right direction for the platform. We wouldn't call this 2.0 if I wasn't deeply convinced that is is the future of deployment and code execution.
like-fill
8
It's true that *some* use cases are still not addressed, which is why we didn't just phase out v1. We are working on a lot of very exciting features, builders and integrations that I'm confident will make all your web applications work great on Now 2.0.
like-fill
4
We have been exploring the tradeoff space between processes and functions, containers and lambdas, for a long time. We understand the problem extremely well, and we have seen and learned first hand what scales and what doesn't.
like-fill
4
Are you planning to support deployment of, e.g., web services with multiple endpoints, implemented e.g. with Python Flask, without making changes to the code?
How about websocket over lambda ? I would be happy to refactor a monothlic to lambda, as soon as it supports websocket connection. Thanks.
like-fill
2
we are investing quite a bit into our Python builder right now, as a matter of fact. We have a lot of good news coming for the python community :)
like-fill
2
That's one of our top priorities to address. As the creator of socket.io, I know exactly what works and what doesn't. I have been researching realtime apps for a very long time now, and I'm confident Now is going to be the best place to host them and scale them to billions of users.
like-fill
11
Here's the kind of interesting thing. Now is a unique company in that we're never going to lower the bar of ambition. We think we can give you the best of both worlds: ease of use and planet-wide scalability.
like-fill
4
Throughout a journey like this, you'll find that some initial assumptions sometimes need to be tweaked.
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.
like-fill
2
Please 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
like-fill
1
It's really not a bad tradeoff to make, all things considered.
I meant it when I wrote in the blog post that my main priority is to address all the customer workloads perfectly.
like-fill
4
I also wouldn't be calling this 2.0 if we had to reject entire classes of interesting applications.
like-fill
8
Also, everyone is free and welcome to email me directly at [email protected]
like-fill
4
And I'm happy to jump on a call with any teams that need further reassurance.
like-fill
3
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.
Edited
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?
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
like-fill
6
All of these will be addressed, and others as well!
like-fill
1
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.
Show more messages