4 ms·

And even then in the Google Cloud console I still feel that parts such as Stackdriver are, in fact, completely separate parts of the UI and not integrated into

And even then in the Google Cloud console I still feel that parts such as Stackdriver are, in fact, completely separate parts of the UI and not integrated into the bigger whole. Same for many other products. Which begs the question, what problem are they solving with this “unification but actually not” approach? Couldn’t they just bite the bullet and give up on the unification and be done with it? Phrased differently, what are the advantages of this unification and reuse of components, exactly?

azurezyq 6y ago
Stackdriver was acquired: https://techcrunch.com/2014/05/07/google-acquires-cloud-monitoring-service-stackdriver/ https://techcrunch.com/2014/05/07/google-acquires-cloud-moni... The problem is that single-entrance is very valuable for ease-of-discovery. But complete integration / unification is just too difficult for something already present since they may simply use a totally different tech stack. Re-writing may not be justified by ROI. For those kind of "separate parts", I can easily mention a few: 1. Stackdriver (acquired). 2. Cloud Data fusion (acquired, formerly cask.io) 3. BigQuery (predate GCP) 4. DataPrep (partnership)
shadowgovt 6y ago
The stackdriver acquisition was a big eye-opener for Google. Well, should have been. I don't know if they actually learned any lessons. ;) In theory, they expected merging SD into the GCP UI to be straightforward, because they're both Angular. In practice... Angular is a framework for inter-component communciation, not an SDK. And it's not a profoundly opinionated framework---the way the two codebases use Angular is so wildly disjoint that a merging was basically impossible without a rewrite. They don't even use the same date-time libraries. One does wonder why they don't give up on the unification model.
steren 6y ago
Stackdriver Monitoring is now fully merged into the Cloud Console.
- cyral 6y ago
  For quite some time too.

azurezyq 6y ago

Stackdriver was acquired: https://techcrunch.com/2014/05/07/google-acquires-cloud-monitoring-service-stackdriver/ https://techcrunch.com/2014/05/07/google-acquires-cloud-moni... The problem is that single-entrance is very valuable for ease-of-discovery. But complete integration / unification is just too difficult for something already present since they may simply use a totally different tech stack. Re-writing may not be justified by ROI. For those kind of "separate parts", I can easily mention a few: 1. Stackdriver (acquired). 2. Cloud Data fusion (acquired, formerly cask.io) 3. BigQuery (predate GCP) 4. DataPrep (partnership)

shadowgovt 6y ago

The stackdriver acquisition was a big eye-opener for Google. Well, should have been. I don't know if they actually learned any lessons. ;) In theory, they expected merging SD into the GCP UI to be straightforward, because they're both Angular. In practice... Angular is a framework for inter-component communciation, not an SDK. And it's not a profoundly opinionated framework---the way the two codebases use Angular is so wildly disjoint that a merging was basically impossible without a rewrite. They don't even use the same date-time libraries. One does wonder why they don't give up on the unification model.

steren 6y ago

Stackdriver Monitoring is now fully merged into the Cloud Console.

cyral 6y ago
For quite some time too.