3 ms·

In theory this sounds awesome but I have to say that demo was pretty underwhelming. It looks like there's a bunch of configuration that needs to be done to ensu

In theory this sounds awesome but I have to say that demo was pretty underwhelming. It looks like there's a bunch of configuration that needs to be done to ensure this is set up properly, not the least of which is that the app needs to be running in a Docker container? Thats a non-trivial task that I don't need to do on Heroku. This seems to be targeting smaller, one off, services not full stacks? Can I deploy my whole cloud at once? Not to mention no talk of how does your app connect to your database? Or caching? Or static assets? Do I need to translate paths in my apps to new domains? Does it transfer my DNS listings? What about auth? Does it translate Cognito to GCP or Firebase auth? What about the data itself? Does it transfer my data between clouds? Lots more questions than answers here.

igorzij 5y ago
Thank you so much for sharing this feedback! Super helpful. It is actually for full stacks, not individual services. The demo isn't doing a great job showing it indeed. Re Docker - yes, we don't believe there's any practical reason running backend code without containers in 2021, unless it's serverless functions. It's easy to dockerize pretty much any app, takes minutes and makes your code portable, container registry becomes your artifact store, easy rollbacks, consistency etc. Connection to DB is done via env variables, automatically mapped from Terraform outputs. Secrets are stored in AWS parameter store or equivalent. Static assets go to block storage (like s3) and served via cdn (like Cloudfront) DNS / domains: each service gets its own unique URL in every environment via managed DNS (on AWS it's route53). You can also connect your own domain. Auth - we don't support that yet, on the roadmap for Q4. Data transfer - no, that's left to the user. We don't anticipate people doing migrations too often though - we just make the infrastructure part simple. Thanks again for asking these questions!

igorzij 5y ago

Thank you so much for sharing this feedback! Super helpful. It is actually for full stacks, not individual services. The demo isn't doing a great job showing it indeed. Re Docker - yes, we don't believe there's any practical reason running backend code without containers in 2021, unless it's serverless functions. It's easy to dockerize pretty much any app, takes minutes and makes your code portable, container registry becomes your artifact store, easy rollbacks, consistency etc. Connection to DB is done via env variables, automatically mapped from Terraform outputs. Secrets are stored in AWS parameter store or equivalent. Static assets go to block storage (like s3) and served via cdn (like Cloudfront) DNS / domains: each service gets its own unique URL in every environment via managed DNS (on AWS it's route53). You can also connect your own domain. Auth - we don't support that yet, on the roadmap for Q4. Data transfer - no, that's left to the user. We don't anticipate people doing migrations too often though - we just make the infrastructure part simple. Thanks again for asking these questions!