clarify future support of docker on now platform
November 8, 2018 at 6:21pmThe ZEIT community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →
clarify future support of docker on now platform
November 8, 2018 at 6:21pmIt seems zeit is moving away from allowing customers to utilize Docker as a common 'primitive'; would you kindly clarify this?
November 9, 2018 at 7:58pm
it does
that was never possible to host to begin with, we only ever supported non-durable workloads
But we definitely want to make it super easy to connect and set up elasticsearch clusters
That's a big use-case we are looking into.
it does
Any example for it ? It looks awesome. Imagine it will allow us to incrementally refactor big monothlic to lambdas.
Any example for it ? It looks awesome. Imagine it will allow us to incrementally refactor big monothlic to lambdas.
Just
version: 1
will work! We mention this in the upgrade guide. That's also why all existing users have to actually go out of their way by specifying version: 2
to upgrade. We didn't want to hurt any existing use-cases. new subscriptions will also work with
version: 1
in now.json
until full compatibility is achieved.(Notice that the new model also dramatically simplifies the gateway aspect of things)
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
that's a very great way to do an incremental migration. Good decision. What I would do is set up an alias for your new v2 monorepo (e.g.: v2.api.company.com), and then use path alias for your current production app to start progressively migrating paths.
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?
This conversation has been locked
This channel has been archived