Paulo De Mitri@paulogdm
Show previous messages
clarify future support of docker on now platformNovember 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 more messages
November 9, 2018 at 9:56pm
November 9, 2018 at 9:56pm
yeah just discovering that too -- that's super concerning. , is there a way to downgrade to a legacy plan? I'm not able to deploy any of my apps to v2 and am now going to be paying $18 per month per deployment
same for you Alin!
not at all proprietary, and not at all specific to our cloud
Meaning: it's just another API, like Stripe
thx for answering some questions here and shedding some light on the motivation to move to a lambda future for Now.
My last thoughts on this.
In terms of scalability your absolutely right lambda functions do scale very well. But you know what also scales really well? An index.html file on a cdn. The reality of real world applications is that there is often loads of complexity to deal with. As much as we engineers try to push back on the requirements there is often just no way around that.
Many of us have been to lambda land and saw it was not as elegant and graceful as it's often portrait in hello word examples. Maybe you guys can change that.
When you say: "We will provide good alternatives for the vast majority of use cases that are hard in a lambda environment." I really believe you and I think you and your team of awesome engineers will do a great job at that. But in this statement there also lies the problem. You will never be able to cater to everyone's needs. That's just what I liked so much about your "docker as a primitive" vision for cloud computing. You guys just needed to get really good/fast at orchestrating and optimizing docker containers and anything could be done on the service.
Building such a system, as you guys did, is probably hard as hell but I could not agree more with : "why the rush to get rid of serverless docker? It is still an amazing product, that has a massive competitive advantage over any other offering I've seen!"
I was so delighted to see all these new examples in the repository. Who ever thought we would be able to deploy Wordpress on Now. I just felt like you guys were really on to something revolutionary... and now you are just one of many.
Sorry if I sound harsh but you must understand that such a dramatic shift in the product direction is going to leave some customers/fans disappointed about the future of product. Than again, disappointing customers sometimes exactly what you have to do to achieve your vision.
I will try to move a few of my personal projects to v2. The company wide decision to move to Now is of the table for now.
Are there any other providers that allow you to upload a Dockerfile? Besides heroku? I don't know if I ever plan on moving to a serverless model. I could wrap my express app with
/node-server, but I'm not sure that would provide out-of-the-box support for websockets.
I'm not certain, at this point, if my entire app that I've built on express and FeathersJS would ever jive with serverless architecture. I feel it'd be a major rewrite.
I don't get it. So with Docker, I can write and app, put it on now, or Digital Ocean, or if the client demands it, run Docker on their physical server in office, or unwrap what is in the Docker container and run it the old way on a real machine without the container...
With the new Now Lambda, I cannot do that. It will be suck require it to be hosed on NOW's platform. Surely, I can move it around on the cloud provider you guys support (AWS, GCE), but there is no way to deploy it to other standalone server / computers?
I was referring to the idea that if there was some sort of wrapper that turns my plain Python Flask app into a Now-compatible web app, i.e. it analyzes the routes in my Flask app and "magically" exposes each route as a standalone function that can be served through Lambda, then I'd write my Flask app as always, write a Dockerfile as always for on-premise (or generally non-Now) deployment, and deploy it on Now with the wrapper.
Hyper.sh is the closest to the (old-) Now model, but as far as I know they require you to have an image stored in some registry before you can launch it there.
I get the idea and even though i wont go in that direction your expertise is propably right that this is the cheapest and best way to move forward. But however good it might be, it is still a lockin. It does not matter that i can choose where to distribute it behind the scenes. I can move a docker setup to wherever i want, even my own servers if i need to. With the new v2 this is a different story, it sounds way more locked in. And i kind of lost a good amount of trust atm. Maybe thats unfair and i am wrong. Actually i hope i am wrong 😕