Google Cloud Virtual Private Cloud (VPC) Reviews & Insights

Most of the microservices I use are deployed in Cloud Run. I configured a serverless connector for these services to communicate with each other privately. The serverless connector can be configured with min and max number of instances so that it can automatically scale based on workload. Being serverless the cost of using the connector works out low for my use case.

Google Cloud Virtual Private Cloud (VPC) is well suited to use when you have micro services that need to communicate with each other privately. When the micro services are deployed as Cloud Run services or Cloud Functions then you can use a serverless connector for communications between the micro services. It would be useful if the product can provide some recommendations to configure networking in cloud for best performance.

I use Google Cloud Virtual Private Cloud to manage our Google Cloud resources across the company. Our scope is across the US, as we serve businesses in each region and aim to keep information stored and attainable across every state.

I think Google Cloud Virtual Private Cloud is more appropriate in a situation where you need the table stakes features of a public cloud with the security of a private cloud.

Google Cloud VPC is used in hosting databases and compute instances. We leverage VPC for connecting instances to databases within the same VPC and have full control of inbound and outbound traffic. We majorly work on big data use cases were within a single GCP project and we make use of VPC to have connections between different services with firewall rules.

Google Cloud Virtual Private Cloud is across all regions in a project. It allows monitoring traffic. It can be used for multiple types of scenarios of the project which includes high secured or want to allow traffic with firewall rules set on each port number and with IP address range. Allowing internal IPs to access or allowing everyone on the internet to allow on a certain port. Google VPC can be shared and allows VPC peering.

Google Cloud VPC will be used more widely in the next years as our own compute engines grow in number. Google Cloud VPC's per-compute cost is significantly cheaper than that of other Compute service providers, and its performance is also comparable. With Google Cloud VPC, new features and services are launched at a snail's pace. Even the technical support may be improved upon.

An effective pricing strategy is in place. Google Cloud VPC is the most secure since it runs on a private network and never contacts the public network. Google is well-known for its AI/ML and Kubernetes engines, both of which have a leg up on the competition. Google Cloud VPC's database services are yet to be improved.

I use Google Cloud Virtual Cloud to store Biometrics Employee Verification Informations (Fingerprint, Photos, Digital Signatures, and Textual data/Biodata). It helps me do data Analytics and presentations for Decision making. VPC addresses the problems of scalability, processing, and control of how workloads. We intend to use it more in Digital identity and delegated authentication of information, this might even go as far as linking it to the Blockchain for purposes of Identity.

Very Good for Data Analytics and Development of APPs

We were looking to use Google VPC to host applications because it was known to scale well, set up was relatively easy, and the pay-as-you-go system proved to be cost-effective for our purpose. This also allowed us to provide better services and to show stakeholders the value of the work.

VPC is well suited for migration from on-prem to the cloud and allows use of all the other computing resources that GCP has to offer in a scalable manner. However, if the data is highly regulated or require auditing, keeping it up on a private cloud on-prem may still be the best option.

Our educational institute comprises hundreds of departments. Each department has up to a thousand employees. Using Google Cloud Virtual Private Cloud we were able to create subnets for each department. This allows each department to have its own virtual private subnet thus, increasing security. Using VPC makes us possible to restricts access between departments and helps to maintain privacy and confidentiality between various departments or research teams. Only specific administrators or higher authority people using static IP addresses could access more than one private subnet. This product has greatly reduced our work of implementing subnetting from scratch.

Well-suited scenarios: 1. Large Organisations with more than at least a thousand employees. 2. Teams spanning across multiple countries or regions. 3. Research institutes require privacy and confidentiality. 4. Educational institutes to separate departments from various attacks.
Less appropriate scenarios: 1. Startups have less than 100 employees. 2. Users are accessing resources from the same place.

We needed a personal cloud to host our offerings. Based on our necessities I recommended going with Google Cloud VPC. The motive behind the choice was the pricing and the availability of their carrier and google's pay-as-you-pass model. We had been capable of hosting their utility and statistics at decreased prices in GCP throughout numerous vicinity and zones. Lastly, it's extremely easy to use.

Google Cloud Virtual Private Cloud would be best suited when the person or the company who plans to implement it actually knows how to use it. Although it is extremely easy to use, if implemented without suitable expertise, it might require some training sessions. So if it's a completely new organization, then implementing and maintaining this would take a lot of time and expertise.

For now we are using Google Cloud VPC for Cloud storage (Object Storage) and Cloud SQL (MySql). We have few Compute engines also and we are planning to use Google Cloud VPC more extensively in coming years. Per compute cost in Google Cloud VPC is much lower as compared to other Compute service providers and performance is competitive.

Pricing model is good. Security wise Google Cloud VPC is best as it runs on private network by default and never touches Public network which makes it very secure. Google's AI/ML and Kubernetes engine are among the best and it has lead over other service providers and google is known for these. Google Cloud VPC has yet to improve on their Database services. The pace of launching new features and services are very slow with Google Cloud VPC. Also the technical support still has room to improve.