clarify future support of docker on now platform
November 8, 2018 at 6:21pmThe 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:21pmIt seems zeit is moving away from allowing customers to utilize Docker as a common 'primitive'; would you kindly clarify this?
November 9, 2018 at 7:40pm
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 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
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.
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.
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
All of these will be addressed, and others as well!
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.
I think , the
now.json
should accept all versions. It will make all of us happy ! it does
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.