Eek - that's an oversight on our side during the PDF creation (copying from the github readme to Indesign) -- it was suppose to be on the PDF. We'll update.
I see some Google Cloud folks in the comments, so question for you, if you're able to share:
There seems to be a general fear about Google potentially killing off a product, based on recent history [1]. Now I know most of these are on the consumer side of things, but you can imagine people's concerns if the same thing started happening to Google Cloud products. Is the GCP team aware of these concerns, (or is this just a HN crowd concern) and if so, are there steps being taken to address this perception head on?
When a company like Deutsche Bank [1] signs a 10-year deal, you can be sure that they have been convinced that the products they rely on will not go anywhere.
https://github.com/gregsramblings/google-cloud-4-words -> this is where the PDF appears to be generated from, and it has searchable text of the content in its README on the main page, and links to docs on each, and the mobile content that got left off the PDF.
"Google cancels everything" is a meme, but AWS releasing broken pre-alpha products, letting old ones rot on the vine, and having crazy monetization schemes that are utterly inconsistent with marketing is not a meme, even though they do these things all the time. If GCP wants to win, they need to fix that, because "will I be blamed for the next shitshow" is the key question on every architect / purchasing manager's mind, and right now AWS is winning that battle to a degree that they do not remotely deserve because google is just MIA.
Hell, Google could coordinate with Walmart to hit AWS and Amazon at the same time because there is clearly, shall we say, a degree of cultural continuity between the Amazon and AWS business units.
What kind of marketing? Google cloud is a highly complex B2B product. Do you know what salesforce or oracle sells? As both a developer and consumer, I have no idea.
This is a point in GCP's favor, since it generally has sane product names. By comparison, to quote some recent Corey Quinn snark, AWS has Lookout for Equipment, Trainium, Glue Elastic Views and SageMaker Data Wrangler.
The major cloud providers REALLY need to focus on fixing years old bugs in their widely used offerings instead of launching new ones. I guess the incentives are out of whack tho, since a working and widely used but slightly broken offering will be used by their existing customers. But if a competitor beats them to the next major thing, they will lose customers as they migrate over to use it. So they're in a kind of arms race against each other to roll out new seemingly obscure offerings in case one of them becomes the next thing and sees widespread adoption.
I wonder if it would be possible to run a site where people submit and rate bugs/enhancements/workarounds in cloud products. E.g. AWS Config doesn't support service X or sharing ENIs across NLB target groups can ruin your day.
What's the use case for something like "VMWare on Google Compute" is it just a API shim to translate VMWare API calls to GCE for companies that are trying to lift and shift to the cloud?
We use it, I'm not on the team that uses it. Basically a lift and shift of our backup data center which came with all sorts of improvements. It's quite a bit more expensive, the projects that it runs in cost more than the rest of our cloud costs in total. But the man hours we've done to set up those other cloud systems (Terraform) are much more costly.
It's a full managed (bare metal) VMware environment.
Basically you get a dedicated cluster of vSphere hosts, with VSAN storage.
Some use cases are: migrating to cloud (for all kinds of reasons, like not wanting to invest in own datacenters and HW anymore) without having to refactor applications, hybrid applications where the front end lives in Google Cloud but the backend requires a more 'traditional' environment, using the cloud for DR, ...
Yeah, I will need a "Google Cloud products in 4 words or less" in 32 words or less, for some cases.
On serious note, I also think it will be good for them, if they mention the 4 word explanation as a sub-title where ever they mention the name. Also applies to AWS.
If you need to publish this you have a product management problem. Arguably, some of these things are features not products, and should not be branded.
The level of complexity is overwhelming, especially for the decreasing marginal returns to effort for most companies for most of these services, I suggest that G and AWS need to take a new approach here.
I'm trying to figure out what the different colour headings mean. Perhaps green means they are keeping it, red means 'scheduled for retirement' and orange is 'we arent sure yet'.
zbowling|5 years ago
Mobile (Firebase)
* Cloud Firestore: Document store and sync
* Cloud Functions for Firebase: Event-driven serverless applications
* Cloud Storage for Firebase: Object storage and serving Crashlytics: Crash reporting and analytics
* Firebase A/B Testing: Create A/B test experiments
* Firebase App Distribution: Trusted tester early access
* Firebase Authentication: Drop-in authentication
* Firebase Cloud Messaging: Send device notifications
* Firebase Dynamic Links: Link to app content
* Firebase Extensions: Pre-packaged development solutions
* Firebase Hosting: Web hosting with CDN/SSL
* Firebase In-App Messaging: Send in-app contextual messages
* Firebase Performance Monitoring: App/web performance monitoring
* Firebase Predictions: Predict user targeting
* Firebase Realtime Database: Real-time data synchronization
* Firebase Remote Config: Remotely configure installed apps
* Firebase Test Lab: Mobile testing device farm
* Google Analytics for Firebase: Mobile app analytics
* ML Kit for Firebase: ML APIs for mobile
gw5815|5 years ago
musicale|5 years ago
sethvargo|5 years ago
Disclaimer: I work for Google Cloud.
jabo|5 years ago
There seems to be a general fear about Google potentially killing off a product, based on recent history [1]. Now I know most of these are on the consumer side of things, but you can imagine people's concerns if the same thing started happening to Google Cloud products. Is the GCP team aware of these concerns, (or is this just a HN crowd concern) and if so, are there steps being taken to address this perception head on?
[1] https://killedbygoogle.com/
mrtrustor|5 years ago
[1] https://www.bloomberg.com/news/articles/2020-07-07/google-de...
(Google Cloud employee here)
6gvONxR4sf7o|5 years ago
Thev00d00|5 years ago
spicyramen|5 years ago
wcarss|5 years ago
sethvargo|5 years ago
Disclaimer: I work for Google Cloud.
jnwatson|5 years ago
jjoonathan|5 years ago
"Google cancels everything" is a meme, but AWS releasing broken pre-alpha products, letting old ones rot on the vine, and having crazy monetization schemes that are utterly inconsistent with marketing is not a meme, even though they do these things all the time. If GCP wants to win, they need to fix that, because "will I be blamed for the next shitshow" is the key question on every architect / purchasing manager's mind, and right now AWS is winning that battle to a degree that they do not remotely deserve because google is just MIA.
Hell, Google could coordinate with Walmart to hit AWS and Amazon at the same time because there is clearly, shall we say, a degree of cultural continuity between the Amazon and AWS business units.
folkrav|5 years ago
enos_feedler|5 years ago
duxup|5 years ago
andrewprock|5 years ago
int x; // variable x stores ints
Clewza313|5 years ago
ciguy|5 years ago
jcims|5 years ago
notabee|5 years ago
paxys|5 years ago
lultimouomo|5 years ago
That's glaringly cheating.
rrdharan|5 years ago
Bigtable -> Big Table
simonw|5 years ago
meddlepal|5 years ago
longcommonname|5 years ago
lode|5 years ago
Some use cases are: migrating to cloud (for all kinds of reasons, like not wanting to invest in own datacenters and HW anymore) without having to refactor applications, hybrid applications where the front end lives in Google Cloud but the backend requires a more 'traditional' environment, using the cloud for DR, ...
Similar offerings exist at other hyperscalers:
* Amazon: VMware Cloud on AWS - https://cloud.vmware.com/vmc-aws
* Azure: Azure VMware Solution - https://cloud.vmware.com/azure-vmware-solution
* IBM: IBM Cloud for VMware Solutions - https://cloud.vmware.com/ibm-cloud
* Oracle: Oracle Cloud VMware Solution https://cloud.vmware.com/oracle-cloud
* Alicloud: Alibaba Cloud VMware Solution https://www.alibabacloud.com/press-room/vmware-based-cloud-t...
[Disclaimer: I work at VMware]
mrtrustor|5 years ago
callesgg|5 years ago
udev|5 years ago
jtylr|5 years ago
pibefision|5 years ago
sytse|5 years ago
tyingq|5 years ago
https://www.awsgeek.com/AWS-Periodic-Table/
https://www.awsgeek.com/AWS-History/ or, as JSON https://github.com/AwsGeek/aws-history/blob/master/services....
stepri|5 years ago
nobrains|5 years ago
migrate VMs to GKE containers
cloud API gateway
dynamic web maps
managed service mesh
Yeah, I will need a "Google Cloud products in 4 words or less" in 32 words or less, for some cases.
On serious note, I also think it will be good for them, if they mention the 4 word explanation as a sub-title where ever they mention the name. Also applies to AWS.
irrational|5 years ago
For instance, what are AWS Lambdas called in Azure and Google Cloud?
decafbad|5 years ago
jariel|5 years ago
The level of complexity is overwhelming, especially for the decreasing marginal returns to effort for most companies for most of these services, I suggest that G and AWS need to take a new approach here.
dash2|5 years ago
unknown|5 years ago
[deleted]
ssijak|5 years ago
ss64|5 years ago
imwillofficial|5 years ago
collyw|5 years ago
unknown|5 years ago
[deleted]
idlewords|5 years ago
makecheck|5 years ago
azhenley|5 years ago
senectus1|5 years ago
Anther|5 years ago
Not going to last.
vidanay|5 years ago
(They just haven't announced many of them yet)
ceejayoz|5 years ago
hateful|5 years ago
follower|5 years ago