Unclaimed: Are are working at Google Cloud ?
Google Cloud is a suite of cloud computing services offered by Google, providing a range of hosting and computing options for web applications, data storage, and machine learning projects. It includes services such as Google Compute Engine, Google Cloud Storage, and Google Kubernetes Engine, supporting businesses and developers in building, deploying, and scaling applications across a globally distributed infrastructure.
( 1 )
| Capabilities | 
             | 
        
|---|---|
| Segment | 
             | 
        
| Deployment | Cloud / SaaS / Web-Based | 
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support | 
| Training | Documentation, Live Online, Videos, Webinars | 
| Languages | English, French, German, Indonesian, Spanish | 
          Compare Google Cloud with other popular tools in the same category.
In Google CLoud run Permits to preform Batch processing and Schedule our Run processing and Scaling the load, from the use of we can build the Graph, Microservices over Hyper text tranfer protocol (HTTP) .
The UI Use interface is not good and it is little bit costly and the integration is not smooth as per standards.
THe Scalibility of GCR is very good and outstanding and integrate with Google services and managing container management and migration is awesome.
Smooth integration, supports various languages and tools
It may have a learning curve, especially for beginners
Handling concurrent builds effectively, ensuring development workflow remains smooth
It is effortless to use for non-data-related users. You do not need to know how to write SQL to create custom tables to analyze data from your warehouse.
The visualization part of the tool is not the best, and you can have many redundant views. Data could be hard to find if the integration is not done correctly.
It simplifies data management and analysis without querying. It makes marketing analist nondata related come up with cool analysis
It has support for almost all RDBMS in the market like Microsoft SQL Server, Psql and Mysql. Etc, easy to configure flags. Virtual database for application development. Easy migration of previous database to virtual cloud google sql cloud. Best feature 9f the Google Sql cloud is that replication of data.
Great API integration for the cloud. No drawback at all.
Can be used for building databases for application development.
It supports containerized applications, making it easy to deploy and manage software in a consistent and portable manner. Users are billed based on the actual resource consumption which provides cost efficiency as you only pay for the compute resources used during request processing.
Users need to containerize their applications, which might be an additional step for those not familiar with container technologies. While Cloud Run integrates with Google Cloud's networking services, it may have some limitations compared to traditional virtual machine-based solutions.
It seamlessly integrates with other Google Cloud Platform services which enhance the overall development and deployment ecosystem. It supports multiple programming languages and frameworks, providing flexibility for developers to choose the tools they are comfortable with. Designed for stateless applications, Could Run suits a variety of use cases, particularly those with short-lived and stateless workloads. Users are billed based on actual resource consumption, offering cost savings by avoiding charges for idle resources and enabling efficient budget management.
Various RDMS Supported such as MySQL, SQL Server and many more. Free credits for new users, ease of use and again supported various and multi database engines. Kubernetes integration.
No thing as such to highlight, Server availablity.
Vendors databases migrations and modernations using SQL.
Flexible build environment - Default or private pools let you choose a build environment that fits your needs. Broad language and framework support - Build apps in Java, Python, Node, Go, etc. Wide ecosystem support. Easy to start - Setting up build through UI or YAML config is quick and straightforward. Integrates with GitHub, GitLab, etc. Automated deployments - Many pre-built deployment integrations with Google Cloud (GKE, Cloud Run, etc.). Can fully automate deployments.
There is no direct support for building Windows containers or executables—only a Linux build environment. Private pools add management overhead compared to default pools. You have to create and manage the VMs yourself.
Automates the CI/CD pipeline - The integration with GitHub, GitLab, etc., for triggering automated builds and deploying tools like Kubernetes Engine streamlines my continuous deployment flow. Enhances security - Features like binary authorization, container vulnerability scanning, and artifact signing help improve my software supply chain security. Standardizes processes - Configuration as code via YAML creates consistency and reproducibility in my builds.
The seamless scalability and robust performance of Google Cloud SQL stand out, ensuring a reliable and efficient database management experience.
the pricing structure of Google Cloud SQL complex and potentially challenging to estimate accurately, leading to cost concerns for certain usage patterns.
Google Cloud SQL addresses the challenges of database management by providing a fully managed, scalable, and secure relational database service. This benefits users by eliminating the need for manual maintenance, ensuring high availability, and allowing seamless integration with other Google Cloud services. The automated backups and updates enhance data reliability, enabling users to focus on application development rather than database administration tasks.
It provides a seamless and easy deployment feature
Nothing,I didn't face anything from Google cloud build.
It solves so many problems and make our automation easier
- This service by google is really very fast and provides realtime solution - Affordable service according to the features given - Highly scalable - Customization options available
- Timeout is set to be very small, everytime asks for sign-in - Due to serverless service, it is less preferred for storing for long time
- Managing containerized microservices - Servless so I can operate it from anywhere, anytime according to my need, with proper sync speed