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:03pm
November 9, 2018 at 8:03pm
Yes, I absolutely love the ability to use the filesystem itself instead of path aliases. Hosting all endpoints in a single source tree is killer DX
It's not even just the best possible DX. It builds faster. It's more secure, by isolating parts of the application from one another at execution time, but not in the source code organization.
Now you are speaking my language. I think that's the true way to scale realtime communication.
For example, your stateless endpoints can populate a queue that gets consumed by a client over a websocket connection
So, you don't put all your eggs into one server basket, and you neatly separate responsibilities.
I'm not as concerned as others on this thread, as all my projects will work fine on the new platform. That being said, I literally just migrated earlier this week from 1.0 to the serverless docker "v2" beta :/ I agree that this looks like the future, but 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! Why not two concurrent offerings? Now Lamba & Now Container?
I also loved merging the testing and build phase, and having that all triggered by a github push. It seems unclear how CI fits into this new paradigm. Is that something that would have to be triggered by the
thanks a lot for commenting. current discussions aside I think that now is an amazing innovator and pretty much everything you guys released this far is pretty much ground breaking. I would love to hear your thoughts on the issue of vendor lock-in / app portability though - as a lot of the stuff that is coming is quite unique to Zeit / now. do You think certain elements of zeits stack could become a standard outside of now?
the "rush" is in the interest of truth-seeking. We, and I, learned a tremendous lot from that beta. I learned what works and what doesn't. I truly think this new world shouldn't wait and our customers will benefit immensely from it.
I think these systems are all in competition to one another to a very large extent, and I think this is the winner.
I think all the systems that are embracing the stateful monolithic servers will collapse under their own weight. I think this is also true for the "service mesh" clusters, but those will collapse under both weight and accidental complexity.
So, if you really think that's the future, I'm ok with some customers going in that direction. I think they'll pay a steep price.
That price is not only in the execution cost (paying cents for 100ms of execution vs a monolith running 24x7), but the most concerning part is how much you'll pay for engineering and optimization costs.
- All of your code should use the language / framework APIs, not custom APIs. [This is what I truly think has been holding serverless back! Lots of weird APIs, context objects and API gateway interfaces 🤨]
- All the clients and builder code is MIT licensed and open source, and you can write your own.
But is a custom now json with build and routing that is specific to now but also essential to the workings of the app not by definition lock into now. i am not saying that’s not fair, lots of cloud provider features are proprietary but still offer lots of value. I just try to truly see where now is headed in this regard
Speaking about the price, how is billing calculated for people that can't migrate all of their instances to v2?
For example I upgraded from Premium to Unlimited, but I realized I can only migrate 1 of my 3 services to v2.
I still have a Next.js app with a custom server and a Python server in a Docker instance running 24x7.
How is that going to be billed on the Unlimited plan?
Not more than a
Dockerfileis also a set of instructions that have to be parsed and executed by a runtime, of which many can be written. If anything,
now.jsonis now as simple as it can possibly be. It consists of just two fields primarily:
routesconfig is standard PCRE for