Thank ZEIT Team for the AMA 👏
First of all, I'd like to thank you for creating
micro and all other amazing services/ products and for hosting this AMA. My questions are:
nowdeployments are stateless, what service do you recommend for database hosting?
The "Pro" pricing plan of
nowlooks great, but can be a bit expensive for some. Do you have plans (pun intended) to create a cheaper, 'lite' plan that offers private projects and custom domains while cutting down on other features?
Why did you decide to make ZEIT/now? Is it because you were frustrated with the existing Node.js deployment solutions?
What do you think is the next big thing after React? Web standards and web components?
Are you guys considering adding benefits for students via the GitHub Student Developer Pack?
First off, everything you've put out so far is amazing so thank you for that!
- Micro is great, but it feels like it could benefit from some kind of system for managing a collection of services. For instance, if I made changes to multiple services used by my front-end, deploying to now would give me new URLs for each and I would then have to go update my front-end references to these services. Is there a recommended tool/workflow for handling this or is there something in the works?
- The only thing "missing" from the Zeit ecosystem for deployment is a data solution. Are there any plans for some kind of hosted data persistence solution
How did you calculate your pricing model? You appear to provide way too much value for what you charge, so I worry that you're not making enough to stay in business...
Will you provide an integrated solution for persistent storage for databases, to e.g make deploying simple MongoDB instances without the need for external services?
- How do you decide what to do next?
- Some words about your UX/DX process?
- What help you to keep focus?
- Can you give some details about 'now' backend (arch, design, etc..) ?
What should I avoid hosting on "now"? Docker opens up so many possibilities, but I know persistent storage is not provided.
I would like to thank you for all the projects you have initiated, i insanely love now, next, hyper and serve too! I was wondering, you contribute to OSS a lot, and that's excellent! but, how do you get money incomes? only through now plans? do you plan to launch any other software for profit? thanks and regards!
I'd like to understand how your company works financially. You do a lot of great things and I wonder how you actually pay your bills. Can you share some details on how you structure your time and the time of your employees?
Have you thought about releasing a GraphQL version of your API?
I'm excited about the latest blog post about using
now.json to customize the deployment. Can you talk more about future plans for
now.json and how many knobs you guys plan to expose to us? For example, I'm particularly interested in controlling how
now scales my deployment. Thanks.
As a team, how do you balance OSS developments like hyper or next.js and your main product needs?
Zeit and the Zeit team is amazing! It seems some of you have children/ families? How do you all balance your family life and work life? Thank you.
You seem to have people working from all around the globe. Do you have physical office(s) or do all work from home? How has it worked out?
Can you provide more information about how you scale? If I have a micro service that need a lot of CPU but don't get a lot of traffic, will you scale according to CPU or traffic ?
I would also love to know what you are doing for service discovery?
And thanks for your work!
do you have any plans to offer in-house
now for companies, which cant host their code on someone's else servers?
What are your thoughts on Functions as a Service? Lambda seems to be falling a bit behind in terms of their modern-ness - they're still using early 4.x. Do you see Lambda-like services springing up, or will Lambda be where the majority of FaaS for Node.js lives?
Any chance you might have an in-between plan in the works for those who don't mind OSS restrictions (public folder, etc) but would want custom domains or more deploys?
Considering you have such an international team of GREAT people, what do you think of Trump increasingly closing borders of America? How do you feel Trump's politics affect digital business?
Thanks for all amazing OSS projects, you are releasing.
question is: do you have any plan to improve database aspect of
Could you explain a little (or preferably, in detail) how Now works under the hood? Are you using Amazon ECS? Lambda? Custom solution? Where is the user code ultimately running and how do you scale it?
You've made an impressive product, with a breakthrough concept.
While you're building this awesome thing there's a lot of people, though enthusiastic, that are flooding you with new requests, from doable to totally out of zeit's world.
How do you guys cope with that? Do you stay true to your initial idea or are considering disrupting part of the roadmap?
Micro looks amazing !! DId you guys have plan to provide real world examples / tutorials /documentations for it ?
Is there any plan to support account switching for now-desktop? i personally like to separate projects for clients and personal projects with different accounts/subscriptions, but the switch process is kind of cumbersome now
How do you all make such awesome products? 😀
But on a more serious note, what's next for
now? You've already got support for static sites, Node.js, and Docker, so where is the service expanding to next?
Do you have any plans to bring Now, as a platform, (NaaP?) to a larger business audience - i.e. large companies and Enterprises?
What do you think it's the future of now-desktop? Do you plan having a some UI to allow handle multiple deploys, with their aliases?
will you do something to increase the file size limit of the static assets(fonts, images) in Now.sh?
You are creating amazing products !
- If the now containers is spread around the world and I want to work with AWS RDS or another DBaaS, what is the correct region I should choose to have the lowest latency? why?
Have you thought about a free tier (non-OSS) that lets developers of small projects use the system for awhile while developing? Perhaps you could disable the CDN features, only have one data center, ... disable some other things that aren't required in development/testing but are required for production?
As others have said I'm impressed by what you've done and want to do more, but I can't convince myself that I need to spend another $15/month until it's in production. And then when it's in production $15/month seems too cheap!