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 8:22pm
But is a custom now json with build and routing that is specific to now but also essential to the workings of the app not by definition lock into now. i am not saying that’s not fair, lots of cloud provider features are proprietary but still offer lots of value. I just try to truly see where now is headed in this regard
Speaking about the price, how is billing calculated for people that can't migrate all of their instances to v2?
For example I upgraded from Premium to Unlimited, but I realized I can only migrate 1 of my 3 services to v2.
I still have a Next.js app with a custom server and a Python server in a Docker instance running 24x7.
How is that going to be billed on the Unlimited plan?
Not more than a
Dockerfile is also a set of instructions that have to be parsed and executed by a runtime, of which many can be written. If anything, now.json is now as simple as it can possibly be. It consists of just two fields primarily: builds and routes :)(And the
routes config is standard PCRE for src matching) the old instances will be measured as on-demand of now v1, the new deployments as on-demand of v2
Can you please write the prices for on-demand v1 here? I can't seem to find them on zeit.co since Now v2 has been announced
The difference between Docker and Now is, however, that Docker can be deployed everywhere, also on premise.
the main premise of of serverless is that request-response invocations very rarely run 24x7 :)
you literally only pay for what you truly use
vs having dead space allocated in a server
the same will be 100% possible for Now 2.0, and that's why we're not locking you in and make you change your code
And you'll actually have a greater variety of deployment targets
For example, let's say you go to a company that really strongly prefers using Google Cloud. You'll be able to tell us that you want your deployments to be in affinity to a particular Google Cloud region or account.
Or, let's say you want to go legacy mode and run it in servers that run 24 x 7 that you have to actively monitor and observe and get paged for.
But that's when you start to realize that the whole enterprise of running things on premise will make little sense.