Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

ZEIT

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

ZEIT / Now

How does Now 2.0 relate to the v2 beta?

How does Now 2.0 relate to the v2 beta?

ZEIT/Now · November 9, 2018 at 2:37am

How does Now 2.0 relate to the v2 beta?

ZEIT / Now · November 9, 2018 at 2:37am (Edited 4 months ago)

Last week the following now.json file would cause Now to deploy to a Docker-based solution with a 100MB image size limit:

{

"features": {

"cloud": "v2"

}

}

With today's announcment haa that v2 100MB-image-limit product been discontinued In favour if the new not-Docker-based Now 2.0?


November 9, 2018 at 10:44am

Yep - exactly my thought...

  • reply
  • like

November 9, 2018 at 1:14pm

The community is discussing this topic here: https://spectrum.chat/?t=96985341-e17f-4af4-a330-c726774ed436

  • reply
  • like

November 10, 2018 at 8:42am

@paulogdm I read most of the discussion over at your link but there were more gernal discussion on the future of v1... what we want to know is what will happen to the cloud v2 feature of v1 (also known as Serverless Docker), I would assume it should still function as the rest of v1

  • reply
  • like

Actually it is a pretty intense discussion about where the Serverless Docker (v2 beta) go, how we see the future of the web, how we will cover use cases that does not fit on v2 yet, etc. It is a long topic with lots of inquiries, arguments and responses and I think it is one of the best resources to see why we transitioned from Docker to Lambda.

Answering your question straightway, the "Serverless Docker" is deprecated in favor of our new set of technologies and concepts. The v1 platform will still be live for and can be used until v2 is capable of serving most use cases (like cronjobs, loops, event queues, etc.)

like-fill
1
  • reply
  • like

November 10, 2018 at 12:21pm

@paulogdm Can you please clarify by confirming that the "Serverless Docker Beta" is being considered part of "V1" and will continue to be supported until further notice?

  • reply
  • like

The confusion here is that the Serverless Docker feature was also called "v2"

  • reply
  • like

They need a better naming. All these NOW v2 / Now v1 Cloud v2 talk is going crazy

  • reply
  • like

@nathaniel The Serverless Docker Beta was a beta of Now 2.0, which we quickly realized wasn't the way to go. We have blog posts coming in the next few days to share more of our thinking/conclusions/reasoning.

In short, the Serverless Docker Beta will never exit the beta phase. It will not be shut down any soon (notice we don't yet have a deprecation plan (which, when published, will give everyone at very least 6 months of grace period)), but it'll not evolve into a more production ready product.

like-fill
1
  • reply
  • like

😱 @matheus so there is no point for me to update my existing docker / NextJS code to use it... for the last few months, I have been hinted that I should wrap my NextJS applications into Serverless Docker to start enjoying the benetfits of Cloud v2... quick startup / stop time etc etc :(

  • reply
  • like

@williamli Now 2.0 gives you the exact same benefits of Serverless Docker Beta and much more, without the need of thinking about Docker, containers, scaling settings and so on. In fact, it gives you even faster cold/warm boot times, better even better horizontal scalability and many other benefits.

Edited
like-fill
1
  • reply
  • like

@matheus i am trying to migrate to it right now, just 2 questions

1. Currently, I have a few Docker image hosted running MeteorJS inside, to move to v2, I will need to make a custom Lambda build step for MeteorJS? Docker, currently, is not supported by v2?

2. I am on the Pro plan right now with about 15 to 20 instances running, after I "upgrade" my plan to v2, I will ended up paying more until I can upgrade most of my instances to v2 since my v1 hostings will be moved to the more expensive on demand plan at $0.025/hr?

  • reply
  • like

1. Indeed, we currently don't have a builder for meteor. In the same way that you would need to craft a Dockerfile for meteor (or use something like now-meteor, which was written by community), you'll need to write a builder for v2.

2. Pinging @leo so he can clarify the plan/pricing situation

  • reply
  • like

@nathaniel The Serverless Docker Beta was a beta of Now 2.0, which we quickly realized wasn't the way to go. We have blog posts coming in the next few days to share more of our thinking/conclusions/reasoning.

In short, the Serverless Docker Beta will never exit the beta phase. It will not be shut down any soon (notice we don't yet have a deprecation plan (which, when published, will give everyone at very least 6 months of grace period)), but it'll not evolve into a more production ready product.

Thank you for this response, I have been waiting for something like this from a Team member for a couple days now! It would be awesome if you could get this written up an published ASAP, I believe you are losing customer trust and good will by the minute with such massive uncertainty. Would also be useful if a blog post would introduce some "official" shorthand terms for all the versions/products so we can minimize confusion there (Serverless Docker was/is also referred to as v2). Great to actually hear a minimum timeframe @matheus

like-fill
1
  • reply
  • like

Personally, I think you should call Serverless Docker done, and add it to "v1" with a feature flag. Then keep v1 around for those that need it. You can definitely charge more for the v1 service, I'm sure most that are using v1 but can't move to v2 will gladly pay more.

like-fill
3
  • reply
  • like

November 10, 2018 at 7:21pm

The terminogy is definitely confusing.

  • reply
  • like

If it turns out v1 stays around from the long run, it might make sense to come up with a new name for it. v1 and v2 are very different products - to my mind, v1 is container-based hosting while v2 is more of a "Now Lambda" product.

like-fill
1
  • reply
  • like

November 11, 2018 at 5:45pm

@matheus Looking forward to the blog post about this. Agree that customers need this context to build trust again.

  • reply
  • like