That is a good question. I have built applications with both, so I thought back to the code I wrote for them. My conclusion: it doesn't matter, because the code will be very nearly the same in both cases. So you would pick Firebase or Cloud Run based on which developer experience you prefer. If you like a more integrated experience using fewer tools, go with Firebase. If you prefer container-based development, go with Cloud Run.
Yes, you can set up the CDN later. Just be aware that the CDN respects any cache-control headers in your responses from Cloud Run. If your code doesn't set those headers (or if you discover that they need to be fine-tuned) you may want to revisit your code after you've added the CDN.
Oh nice. How about having Cloud Storage serves static files and App Engine for dynamic file. Backed by Global LB with Cloud CDN? For failure we can add Multi region Cloud storage and Multiple App Engine regional deployments? I haven't tested, just a thought.
That's a great architecture and I've seen others use it for production systems. I didn't call it out in the video because I prefer to use Firebase's automatic CDN over setting up Cloud CDN myself. One caveat to keep in mind: App Engine doesn't support multi-region deployments.
My respects, and thank you very much for providing general solutions and for all levels. We need to know how to work over the phone if it is possible, and we may be able to do it by following the steps, conditions and rules
@@TheMomander I need to become a strong user because I continue to learn and I want to accomplish tasks as well as I study e-commerce and everything is by phone as I cannot buy a computer now and I learned a few basics of programming and why not and thanks for you
@@TheMomander Thank you very much for your interest and appreciation. I would like to inform you that I aspire to learn. I have participated in several courses on the Coursera platform, machine learning, operating systems, java, c++, technical support fundamentals, the bits and bytes of networking.
@@zouhirelmezraoui1336 Sorry, we aren't really equipped to provide one-on-one developer training over the phone. Sounds like you found Coursera. That is a great resource!
Any of the three approaches outlined in this video would work. If you generate the HTML files at build-time, you would treat them like any other static asset. If you generate the HTML on the server for each request, you would do that in Cloud Run or Cloud Functions. You can set it up yourself, but if you are using Nextjs there is less manual setup thanks to buildpacks. You may want to check out our video "Run your Next.js app on Cloud Run" that shows you how to do it.
Good question! Whenever I have used that architecture myself, I have used a single Cloud Run service for both the frontend and the backend. I like how the whole application is a single container. This makes it easy to reason about what is currently deployed and to roll back to a previous version if needed. It also means that CORS will be less of a concern. It is of course possible to create two containers and deploy them separately. That would be useful if you are relying on nginx or similar to serve your static content. It is also useful if you need to scale and optimize frontend and backend separately. But that kind of manual scaling and optimization is not needed as much when you are using a serverless platform like Cloud Run. Best of luck with your project!
I think it depends. Are you streaming video? If so, Cloud Run can handle the regular web stuff, but you will need something different to stream the video. It could be an existing service, like RU-vid, or your own media server. The Google Cloud Marketplace includes a number of media server products.
Very interesting! I’m currently using Google Apps Script to serve some HTML files and building a nice PoC of a possible future application. Maybe your first option with firebase might be the next step. I’ll have a look into it! Btw, love the videos!
Any of the architectures described in this video would work well for that. You just have to think about which pros you care the most about, and which cons you want to avoid the most. Also, don't be afraid to pick the "wrong" one. It's pretty easy to switch between them. Best of luck with your project!
I agree! I especially like how you can access it like a normal database (by putting your own server-side API in front of it) or clients can access it directly without any server-side code. Most of my web apps use a combination of these two approaches.
I have a question. Is it possible to run a serverless, scalable web application (running some custom disaster recovery solution as an example) that is multi-regional/global in Google Cloud? So far all the serverless options that I have seen are all regional.
Yes, when I'm writing this (June 27, 2022) you can host your Cloud Run service in 33 of Google Cloud's 34 regions worldwide. If your Cloud Run service has been deployed to multiple regions, you can either address each region individually, or put a load balancer in front and send each user to the closest one. Check out our video "Speed up your Cloud Run service by hosting it closer to your users" for instructions!
Y0 he entendido que para las personas como yo nos lo quieren hacer más fácil y entendible aparte nos quieren ayudar bievanida sea su ayuda y ustedes también gracias
Le Puedo jurar que hi Oy pos hoy nunca me he sentido más seguro veo que al mismo tiempo velan por sus ltereses y al mismo tiempo por los nuestros también gracias
