Google Cloud Platform vs. Upsun

When most of our stuff is in Google Cloud Platform, it works great to integrate and cross/share data that is all in Google Cloud Platform or BigQuery. It has simplified things from a permissions perspective as well. I'd say it is less appropriate when trying to test something quickly locally, or when half your stuff is in AWS or another provider.

Incentivized

In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.

Incentivized

• Easy to set up
• Affordable use of the tool
• Easy to access billing
• Reliable service

Incentivized

• As this is a PaaS it mitigates the complexities of a Cloud infrastructure like Acquia
• We are easily able to integrate our sites with different technologies like Python and Rest
• Helps us in providing Continuous Development cloud deployment hosting solution

Incentivized

• The UI is so confusing. The console is good, but it is like a maze. There are too many menus and settings, and things do not work as expected. It takes time to get friendly, and it is not friendly for new users.
• Support experience: Sometimes, you get a great engineer, but other times, it's very difficult to talk with them as they are unable to respond as expected and solve issues late.
• Region and zone are issues, as not all services are available in all regions, which is lacking when deploying something in the same region or zone.

Incentivized

• Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
• As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
• During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.

Incentivized

The Google Cloud Platform console is pretty slick for BigQuery especially. I have liked the visibility I get from using that and the way to integrate and see what's in our data lake. The logging console for tracking GKE jobs isn't quite as great, which is why it doesn't get a full 10.

Incentivized

Google Cloud Platform is release later than Amazon web service, I think that why Google Cloud Platform can learned and optimized the Dashboard and some features that make it easy to use and can be cheaper than amazon web service.

In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.

Incentivized

• It allows us to focus our efforts on other, more important items at hand
• It gives us an affordable option letting me know it's available to all users, not just the largest scale ones out there
• The customer service is always helpful and reliable, along with the service itself which lets me focus on my work instead of worrying about the service.

Incentivized

• Continuous development for sites in build has been fluid
• Platform.sh is really cost effective when comparing to AWS or Acquia Cloud
• On the other side, lack of server side support demands a big learning curve from its users in my opinion.

Incentivized