Good question! Identity-Aware Proxy (IAP) and API Gateway are slightly different products. IAP provides a user interface for users to log in with and locks out anyone who isn't on the approved user list. API Gateway provides a simplified API surface in front of your back-end services and lets you monitor it. It does not provide a user interface for login in and you can't give it a list of approved users.
@@googlecloudtech thank you so much! Looking forward to more videos! I am an IT Director for a small non profit and I've honestly been blown away by Google Non Profits so thank you so much!!!!
Yes, you could use a different database. There are two reasons we didn't pick Firebase or Firestore for this architecture: 1. This system handles money and it will probably need to aggregate many records (sums, averages, etc). A traditional SQL database is better at that than a NoSQL database like Firestore. 2. The data in the system, like invoices, aren't tied to individual users. Access rules based on user id aren't as helpful in that case. Hope this helps!
it´s a greath scenary thank you for sharing us talent, I would like to know how to do the exact calculation of this scenario in the price calculator to offer implementation opportunities in my ecosystem, I remain at your service, thank you very much.
You may be able to use a similar architecture to what we used in this video. But it's hard to tell without knowing the details of your application and requirements.
Thank you very much for your kind response, I do not have an architecture per se, it is just trying to take all those tools that you used to the cost calculator and have an approximate cost to use them in future leads@@TheMomander
@@ivanr2159 I understand. My rule of thumb for pricing out a future system is: use serverless whenever possible, to avoid fixed monthly costs. Unless your application has a large user base, those fixed monthly costs will dominate your cloud bill.
This is an awesome way to teach and learn. Kudos to all involved
We're glad to hear you found it useful!
Absolutely liking this use case driven approach to learning!
You guys have such a good vibe😃
That was absolutely great!!!
Good stuff. More use cases please !
Great video. These use cases are so helpful and informative
Excellent stuff. In the design videos, you use IAP. Why do you never include API Gateway?
Good question! Identity-Aware Proxy (IAP) and API Gateway are slightly different products. IAP provides a user interface for users to log in with and locks out anyone who isn't on the approved user list. API Gateway provides a simplified API surface in front of your back-end services and lets you monitor it. It does not provide a user interface for login in and you can't give it a list of approved users.
By the way, the Cloud Run + IAP integration has launched. See the video titled "Cloud Run user auth for internal apps" that was released recently.
This was amazing! I would like to practice whatever it takes for this to be my job everyday! 🤩
I would love this to see for network
In the use case presented here, why did you go for VisionAPI instead of DocAI?
We *meant* the Doc AI. Thanks for pointing this out.
Perfect video
Glad you enjoyed it
@@googlecloudtech thank you so much! Looking forward to more videos! I am an IT Director for a small non profit and I've honestly been blown away by Google Non Profits so thank you so much!!!!
Great video! more of this please
Nice scenario..
Loved them
I like the video towards making design choices and coming up with a final design. Where can I find similar videos?
Can I use Firebase instead of SQL then set user auth , and add rules in firebase.
Yes, you could use a different database. There are two reasons we didn't pick Firebase or Firestore for this architecture:
1. This system handles money and it will probably need to aggregate many records (sums, averages, etc). A traditional SQL database is better at that than a NoSQL database like Firestore.
2. The data in the system, like invoices, aren't tied to individual users. Access rules based on user id aren't as helpful in that case.
Hope this helps!
Great!
The girl made things so interesting!
Nice! :)
Awesome!!
it´s a greath scenary thank you for sharing us talent, I would like to know how to do the exact calculation of this scenario in the price calculator to offer implementation opportunities in my ecosystem, I remain at your service, thank you very much.
You may be able to use a similar architecture to what we used in this video. But it's hard to tell without knowing the details of your application and requirements.
Thank you very much for your kind response, I do not have an architecture per se, it is just trying to take all those tools that you used to the cost calculator and have an approximate cost to use them in future leads@@TheMomander
@@ivanr2159 I understand. My rule of thumb for pricing out a future system is: use serverless whenever possible, to avoid fixed monthly costs. Unless your application has a large user base, those fixed monthly costs will dominate your cloud bill.
I found it sooooo basic...