menu

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 8:26pm
the old instances will be measured as on-demand of now v1, the new deployments as on-demand of v2
  • reply
  • like
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
  • reply
  • like
that’s a fair point, and answers my question. thx
like-fill
1
  • reply
  • like
So if until now I was paying $15/month for 4 instances (2 services deployed in sfo1 and bru1), on unlimited am I going to pay $0.025 * 24h * 30d * 4 instances = $72 ?
  • reply
  • like
The difference between Docker and Now is, however, that Docker can be deployed everywhere, also on premise.
like-fill
4
  • reply
  • like
the main premise of of serverless is that request-response invocations very rarely run 24x7 :)
  • reply
  • like
you literally only pay for what you truly use
like-fill
1
  • reply
  • like
vs having dead space allocated in a server
like-fill
1
  • reply
  • like
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
  • reply
  • like
And you'll actually have a greater variety of deployment targets
Edited
  • reply
  • like
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.
  • reply
  • like
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.
  • reply
  • like
I understand, and I would love to take advantage of Lambda. But I'm in this ugly situation where I can't easily convert my services to lambda. So the pricing has gone over the roof in my case. Can I at least downgrade to Premium until I find a way to convert my services?
  • reply
  • like
We'll give you the wrappers to containerize the app as well (similar to now dev)
  • reply
  • like
But that's when you start to realize that the whole enterprise of running things on premise will make little sense.
  • reply
  • like
So deploying a Python Flask app with multiple endpoints will be possible without Now-specific changes?
  • reply
  • like
Between the option of being paged at 3am to restart a server
  • reply
  • like
Or things running quickly on-demand and paying no maintenance costs
  • reply
  • like
The equation becomes quite simple.
like-fill
1
  • reply
  • like
that's what we are working on right now
  • reply
  • like
In fact, we are doing that because we want to welcome more devs to our platform
  • reply
  • like
But anyone today could be writing a flask wrapper
  • reply
  • like
How would I go about deploying a "traditional" express server with non filesystem-based endpoints?
  • reply
  • like
I legit just recently switched my NodeJS app to use Docker because that's the advice I was given by the team here when I didn't want to use yarn to install my packages. Now I have to switch to something else?
like-fill
2
  • reply
  • like
Show more messages
private
This conversation has been locked
private
This channel has been archived