Ask us about:
- Cloud Computing
- Node.js deployment
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?
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
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'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.
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?
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!