4 ms·
What's wrong with say Dataproc (https://cloud.google.com/dataproc/ https://cloud.google.com/dataproc/) instead of roll your own Spark? Or our (just announced)
by boulos 11y ago
What's wrong with say Dataproc (https://cloud.google.com/dataproc/ https://cloud.google.com/dataproc/) instead of roll your own Spark? Or our (just announced) Machine Learning service based on TensorFlow (https://cloud.google.com/ml/ https://cloud.google.com/ml/)?
I'm all for roll your own if you're building one of these services or have existing infrastructure, but I personally like the simplicity of "here, you set this up".
Disclosure: I work at Google on Compute Engine (which underlies all of these).