Microsoft SQL Server on Cloud SQL is quite laughable in terms of feature sets, it currently doesn't support exporting your tables as JSON or CSV, you can only export as a .BAK file which is some MSFT proprietary trash and this bug https://issuetracker.google.com/u/0/issues/170026117 was open for months with no ETA for resolution.
Google Cloud vs. AWS Onboarding Comparison
251–260 of 394 posts
Re: Google Cloud vs. AWS Onboarding Comparison
#252Earlier quoted context omitted.
I spent over a year doing a full migration from AWS EC2 + ECS instances to GCP + docker + kubernetes. It was a huge task that has paid off very well. 1) Costs per customer are lower because you can fit more containers per VM due to kubernetes doing the scheduling for you. Customers also include developer environments. 2) The number of deploys is way up because there is a simple and established pattern that everyone f…
I know you're only picking on Digital Ocean incidentally here, but their managed Kubernetes offering is Pretty Okay. I use it for my personal stuff and it's pretty much everything I expect from a managed Kubernetes offering. Just don't use EKS. That is managed Kubernetes in the checkbox marketing sense only.
Definitely. I have nothing against Digital Ocean or their offering. It was only an example of a different mindset.
Re: Google Cloud vs. AWS Onboarding Comparison
#253Earlier quoted context omitted.
I've had the same experience with GCP account reps. They always go missing and someone new emails us about how they are taking over 6 months later. Every call we have had with them has not resulted in anything meaningful. Our biggest issue is how their "highly available" Cloud SQL goes down every couple months for maintenance, not how we can use BigQuery.
We’re currently migrating to Spanner for a variety of reasons - but the mandatory downtime on their Postgres CloudSQL offering will be the part I miss the least. It’s insane that even with all of their HA and failover turned on they take the whole cluster down for as long as they like every few months!
I use Aurora just for this reason. RDS is just a great product. Doesn't even need the cloud sql proxy equivalent since you can just install the authenticator into the database.
Re: Google Cloud vs. AWS Onboarding Comparison
#254I don't know why anyone would even consider GCP with Google's track record of no human escalation points and random product/feature/account culling.
If you need a specific service like BigQuery then that's the only service you should have on there.
Re: Google Cloud vs. AWS Onboarding Comparison
#255Earlier quoted context omitted.
I was able to get 130k free GCP credits (over 3 years) just by filling out the startup forms... as a complete nobody. You don't even need an affiliate to sponsor you.
Did you apply via https://cloud.google.com/startup ? I'm in a similar position and those credits would be lifechanging.
Oh you'll pay in the end.
Re: Google Cloud vs. AWS Onboarding Comparison
#256Earlier quoted context omitted.
One thing that customer obsession at an entire-organization-depth level does is encourage broad customer use awareness. To an engineer, things are things, because of how they architect and build them. To an engineer who understands a customer, things are things and all the things people actually use them for. Big difference. It also makes "Well, that customer is using it wrong" less of an exceptable engineering dodge…
Surely product makes these decisions, not engineers, right? I agree that customer empathy is important, but I don't think we can conclude that the engineering team (rather than the product team) is the source of the deficiency?
It's a full-company culture problem where ~everyone has personal responsibility.
Behavioral properties are end-to-end, like speed, security, customer success, uptime, etc. Everyone and everything on the hotpath for that has to be on board, as just one violator means nobody is achieving it. Operationally, part of achieving that means company norms, such as when collaborating, planning, executing, etc.
It's 100% fine not to provide any of these, and is even reasonable given it's hard to change one's DNA end-to-end... but better to be an explicit decision. Likewise, if starting a company... a lot easier to pick & ingrain these habits ahead of time.
Re: Google Cloud vs. AWS Onboarding Comparison
#257Earlier quoted context omitted.
Not the original poster but we migrated to GCP because: 1) AWS was extremely expensive 2) Our GCP bill is about 1/3 of what AWS was 3) The Kubernetes offering is top notch 4) Google giving us credits and offering us consulting were the triggers that started us talking.
What makes GCP's Kubernetes offering better than the competition?
There are several reasons:
- Google has a lot of experience running containerized services because of Borg. Google Research says that they have been running these workloads since 2005.
- The above gives them insight into how to do this well. They would have the internal infrastructure, logging and monitoring already setup.
- They are the creator and still a major contributor to Kubernetes itself which means they can insert their influence on it.
Note: I am responsible for 5 clusters, 300+ nodes total and several thousand running services. Not huge by any means.
Re: Google Cloud vs. AWS Onboarding Comparison
#258Earlier quoted context omitted.
CloudSQL was slow for us until we do the following: 1) Increase the disk size to 100GB as this increases the IOPs 2) Switch to using private IP addresses. Huge speed increase 3) get rid of cloudsql-proxy. Another huge speed increase These 3 things have kept our database instances very small and costs low.
> Switch to using private IP addresses. Huge speed increase. Interesting. I'm looking Cloud SQL right now and the advice seems to lean in the opposite direction: use public IPs for ease of connecting. Can you quantify the decrease in latency? All I can find is bits about reduced network hops.
I honestly don't know what the difference is but the number of hops is probably a contributing factor to the decrease in speed. There could be some translation layer happening when going from the CloudSQL instances private IP to public IP with some security checks that slow it down.
I didn't have to worry about the 'ease of connecting' when using CloudSQL as all my GCP services are in the same VPC.
Also, private ip is one less security problem to worry about.
Re: Google Cloud vs. AWS Onboarding Comparison
#259From personal experience in multiple startups I can confirm that with regards to customer service and sales processes AWS is light years ahead of GCP. That said I have heard even better stories about Azure actually - apparently it is yet in another league of its own in terms of perks and actual service game.
The Azure service game is indeed incredible. Every experience I've had with them has been excellent. A client once requested we file a support ticket with Azure to help deal with a performance issue my team was working through. It wasn't really all that urgent, but the client requested we use the highest urgency level anyway. So I filed our ticket. In less than a minute I felt like my phone was being blown up by ever…
Glad to hear your logging issues didn't turn out to be Fatal for the rest of us.
Re: Google Cloud vs. AWS Onboarding Comparison
#260Earlier quoted context omitted.
I use a lot of Google products. All of them I pay for, except search. It is true there are individuals that shine, but across the board, Google sucks at support. It starts at the top with what kind of company they want to be, and goes from there. They do not like humans.
Once upon a time I was one of 3 people globally that was the entirety of the GCP support team :) You should have seen the extent to which the rest of the team and I tried to resolve customer issues. Random App Engine app getting 500s calling an Open ID endpoint (the service wasn't strictly speaking managed by GCP). I absolutely could not reproduce this and had no other reports, but I knew it was happening for the cus…
One thing that AWS Premium Support does very well is make situations like this seem unremarkable. This is the default way you do work. Going above and beyond is solving the issue, the next issue the customer hasn't asked you about, and giving practical guidance on things like cost optimization or availability concerns after weeks of deep diving.
I'm not saying you didn't do great work, but I think the secret to success at AWS Support is normalizing this level of customer obsession.