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 8:39pm
November 9, 2018 at 8:39pm
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.
Or things running quickly on-demand and paying no maintenance costs
The equation becomes quite simple.
In fact, we are doing that because we want to welcome more devs to our platform
But anyone today could be writing a flask wrapper
Look at the amount of proprietary imports here => https://github.com/zeit/now-builders/blob/master/now-node-server/index.js#L1-L10
What Zeit should realize is that I'm well willing to accept the tradeoff of having an app that is up 24x7 consuming resources (e.g., Docker-style NodeJS app) and paying a few more dollars/cents if that means I don't have to write code like this. In other words, the need for serverless isn't a problem I currently have. I understand that it's more efficient, but those benefits only make a material difference for really large applications.
If I have a low-traffic app, the serverless model vs docker isn't going to make a ton of difference. I'm already only paying $15 a month. Price isn't a top concern.
Getting an out-of-the-box wrappers for Flask apps would be awesome, but I can also see how it can be done manually, now, that you mention it. I totally agree with your arguments in favor of serverless deployment. I'm thinking of the many companies that cannot (for some data privacy reason or other political reason) deploy on Now or even big cloud providers and for those we need to be able to offer on-premise deployment. But we wouldn't want to write an app twice - one for deployment on Now and one for on-premise deployment. A wrapper sounds like a good compromise, at least for some/many scenarios.
As a developer, I believe in your vision, and have benefitted from the sometimes swift learning curves Now has introduced. All I can say is: damn, Man, keep up the great work! I embrace the new model despite the additional work because I know you've put a lot of time and thought into what's going to work more permanently moving forward. I know Lambdas is a once in a generation technological shift now, and I wasn't sure about that until this announcement. Next with React 16.7 is awesome. Love what you're doing. Keep it up!