Google Cloud Platform

Hi

We have 2 web applications running on PHP and Laravel and backend MySQL. Currently, each server is running on a dedicated server. We want to switch to a cloud infrastructure. Looking into either Google Cloud Platform or Amazon AWS.

Which one is better? Google cloud comes out to be a couple of hundred dollars cheaper than AWS.

Need advice on which one we should go with?

Thanks

I am currently working on a long term mobile app project. Current stack: Frontend: Dart/Flutter Backend: Go, AWS Resources (AWS Lambda, Amazon DynamoDB, etc.) Since there are only two developers and we have limited time and resources, we are looking for a BAAS like Firebase or AWS Amplify to handle auth and push notifications for now. We are prioritizing developing speed so we can iterate quickly. The only problem is that AWS amplify support for flutter is in developer preview and has limited capabilities (We have tested it out in our app). Firebase is the more mature option. It has great support for flutter and has more than we need for auth, notifications, etc. My question is that, if we choose firebase, we would be stuck with using two different cloud providers. Is this bad, or is this even a problem? I am willing to change anything on the backend architecture wise, so any suggestions would be greatly appreciated as I am somewhat unfamiliar with Google Cloud Platform. Thank you.

Hello Everyone, My motive is to build an MLOps pipeline that is 100% independent from Cloud services like AWS, Google Cloud Platform, and Microsoft Azure. I have a project for a client in a production factory and would like to build a Camera based Object Tracking ML service for them. I want to build this pipeline in my own server or (on-premise computer). I am really confused about what stacks I should use. I keep ending up with a Cloud component based solution. It would be great to get some advice on what are the components that I can use and preferably open source.

I am new to the cloud platforms. I am trying to figure out which Google Cloud product would be the best fit for my needs. Here are the requirements I am trying to meet:

1. Store data in Google Cloud Platform.
2. Support potentially thousands of concurrent users running analytical queries.
3. The data volumes would be moderate (as far as Google is concerned) - we are talking 10's of GB up to potentially 100s of GB.
4. The data needs to be updated once a day (but ideally a few times a day).
5. Perhaps my biggest goal is the following: I am trying to avoid having to build a traditional data warehouse with star-schema and ETL process. I have experience with these projects, and they end up being very costly, error-prone, hard to troubleshoot, and rigid (hard to deploy changes). Instead, I am hoping to just copy my OLTP tables to GCP and query them from there, relying on GCP horsepower. I appreciate any feedback.

Hello folks, we are making a company internal google chatbot system hosted on Google Cloud Platform. The backend is being written in ExpressJS + TypeScript, we are planning to use Cloud SQL to store basic entities like Users, Spaces, Connections(use-case specific).

The question I have is which tool is recommended for this basic use case where we want to query some data and perform CRUD operations. Also, how we should be handling the DB version control & migrations?

Good day, everyone!

We recently got the request to add a feature to our systems: Forms should be saved to be continued later given the following cases:

If the connection to the server is lost, if the user closes their browser, if the user changes networks, if the user didn't finish the form and decides to take a week off and a mix of them all.

One of the best solutions we've thought so far is to save the data in the forms in a remote database every so minutes directly from the client.

A document-oriented database seems the best bet, but which database to use is the question. Since we already use Google Cloud Platform, Cloud Firestore is a "safe" option right now, but we are looking at every option we can find. The "caveat" of our use case is that we need more writes than reads, but writes are usually more expensive, and our biggest constraint is budget.

That's why I am seeking advice. What other options do we have?

In case you're wondering, we seek to save the forms bypassing the backend and our own system resources entirely, so a dedicated, remote database or Local Storage are our best options, but Local Storage is a bit controversial choice within the team, so we will explore that options later on.

Any advice or experience in this matter is highly appreciated!