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:52pm
November 9, 2018 at 9:52pm
What I don't need is yet another external service for my application to depend upon. What I need is an always-on NodeJS application instance (minimum 1, with the ability to scale as needed) that can handle persistent websocket connections -- unless I'm mistaken and the new architecture will support this.
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.
This conversation has been locked
This channel has been archived