Amazon Web Services vs. Google Cloud Virtual Private Cloud (VPC) vs. IBM Cloud Internet Services

This is something that is actually common across most cloud providers. A comprehensive understanding of one's use cases, constraints and future directions is key to determining if you even need a cloud solution. If you are a 2-person startup developing something with a best-scenario audience of 1k DAU in a year, you would very likely best served by a dirt-cheap dedicated Linux server somewhere (and your options to graduate to a cloud solution will still be open). If, however, you are a bigger fish, and/or you are actively considering build-vs-buy decisions for complicated, highly-loaded, six-figure requests per minute systems, global loadbalancing, extreme growth projections - then MAYBE you solve all or part of it with a cloud provider. And depending on your taste for risk, reliability, flexibility, track record - it might be AWS.

Incentivized

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.

Incentivized

In terms of business challenges, it simplifies the job of my engineers and significantly increases the productivity of my teams when they collaborate with IBM teams all over the world. Now that we have completed a proof-of-concept using the services supplied by IBM, we expect it to assist us in managing them more efficiently; thus far, management has been straightforward.

Incentivized

• During the month-end, we experience high resource utilization; however, with AWS's scalability, we can effectively tackle the peak load.
• With AWS IAM, we don't need to set up complete infrastructure for identity and access management, as AWS provides end-to-end IAM services.
• With AWS, development has become very easy as it's very quick to spin up and destroy the environment, which saves costs.

Incentivized

• Serverless connector helps Cloud Run services to communicate privately.
• Serverless connector supports auto scaling.
• Being serverless, the cost is based on usage for serverless connector.

Incentivized

• Integration with IBM Cloud applications
• Easy to manage web application firewall
• Ease of protecting CloudFoundry applications
• Good console UI
• Protection for rare managed service offerings such as CouchDB through IBM Cloudant

Incentivized

• When there is any misconfiguration of EC2 related to SSM Connect. It doesn't clearly states that what particular configuration is missing.
• Debugging networking related issues could be improved.
• From the security group page, it's difficult to determine which resource a security group is associated with.

Incentivized

• Sometimes the group settings tab lags a little
• Although overall it's easy to use, some of the sections lack documentation
• Routes section is very poorly implemented, requires a lot of digging to learn how to use

Incentivized

• Request proxying is done by way of DNS name resolution, which is inflexible.
• Proxy services do not work on wildcard DNS entries.

Incentivized

We are almost entirely satisfied with the service. In order to move off it, we'd have to build for ourselves many of the services that AWS provides and the cost would be prohibitive. Although there are cost savings and security benefits to returning to the colo facility, we could never afford to do it, and we'd hate to give up the innovation and constant cycle of new features that AWS gives us.

AWS offers a wide range of powerful services that cater to various business needs which is significant strength. The ability to scale resources on-demand is a major advantage making it suitable for businesses of all sizes. The sheer volume of options and configurations can be overwhelming for new users leading to a steep learning curve. While functional the AWS management console can feel cluttered and less intuitive compared to some competitors which can hinder navigation. Although some documentation lacks clarity and practical examples which can frustrate users trying to implement specific solutions.

Incentivized

VPC is a difficult concept to grasp and recommendations for configuring it would be helpful in educating the users to make the right choice while using the product in configuring networking for their cloud deployments. Also, the user interface can be intuitively designed so as to suggest templates to perform common configurations with regard to VPC.

Incentivized

I have seen faster and more user friendly interfaces like Azure

Incentivized

Availability is very good, with the exception of occasional spectacular outages.

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.

The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to
immediately search for their compatible software's and also to guide them in a
good direction. Moreover, this product is a good suggestion for every type of
company because of its affordability and ease of use.

Incentivized

The API's were very well documented and was Janova's main point of entry into the services.

Amazon Web Services fits best for all levels of organisations like startup, mid level or enterprise. The services are easy to use and doesn't require a high level of understanding as you can learn via blogs or youtube videos. AWS is Reasonable in cost as the plan is pay as you use.

Incentivized

Google VPC and networking infrastructure is very matured and is built later after Amazon VPC. It made sure to address all the limitations faced by amazon VPC. Google Virtual private cloud is across regions while amazon VPC covers only one region but multiple zones. Google VPC is a global resource while AWS is a regional resource.

Incentivized

I have used Salesforce to explore it as an app but I have found them both able to solve my needs and requirements when it comes to security. While I choose IBM Cloud Internet Services for more accessibility, a better price was available with Saleforce. Although that is just my observation.

Incentivized

• Using Amazon Web Services has allowed us to develop and deploy new SAAS solutions quicker than we did when we used traditional web hosting. This has allowed us to grow our service offerings to clients and also add more value to our existing services.
• Having AWS deployed has also allowed our development team to focus on delivering high-quality software without worrying about whether our servers will be able to handle the demand. Since AWS allows you to adjust your server needs based on demand, we can easily assign a faster server instance to ease and improve service without the client even knowing what we did.

Incentivized

• Using Google Cloud VPC cloud storage has saved us on infra budget and per TB storage cost
• Using MySQL databases on Google Cloud VPC has improved the performance and cost of operation and maintenance
• Better pricing model has improvement on operational cost and increased revenue

Incentivized

• It had a positive impact with a big improvement on the performance of web applications.
• Services are quite fast to implement and easy to maintain from an IT perspective.

Incentivized