2 ms·
Reads more like an advert for a buffet than a reasoned take on the architectural and business tradeoffs. Detailed price breakdowns are difficult to read? That's
by omegaworks 10y ago
Reads more like an advert for a buffet than a reasoned take on the architectural and business tradeoffs. Detailed price breakdowns are difficult to read? That's your argument? Really? "By developers, for developers!" so original. [0]
I expect more effort to go into this from a technical perspective. Give me some workload / price differentials. Examples of architectures that are simpler on GCP then AWS.
My app relies on a hybrid of Firebase and AWS for the heavy assets. Still trying to justify the move to Google Firebase for the full stack. I'm the only dev so it's time and energy I can't spend on frontend iteration helping real users.
0. http://pbskids.org/zoom/ http://pbskids.org/zoom/
- boulos 10y agoIn a side thread, the quizlet folks mention their real-world experience and reasoning for coming to GCP. In your case, as a Firebase customer, the integration is already there and you could start adding pieces over time. As the integration between Cloud and Firebase improves, I'm guessing you'll find more reason to "just do it on Google Cloud". Ping the Firebase people about their current Alpha programs ;). Disclosure: I work on Google Cloud.