3 ms·
Apparently youtube is: http://code.google.com/p/vitess/ http://code.google.com/p/vitess/ as well as heroku: http://blog.golang.org/2011/04/go-at-heroku.html ht
by stock_toaster 14y ago
Apparently youtube is: http://code.google.com/p/vitess/ http://code.google.com/p/vitess/
as well as heroku: http://blog.golang.org/2011/04/go-at-heroku.html http://blog.golang.org/2011/04/go-at-heroku.html / https://github.com/ha/doozerd https://github.com/ha/doozerd
edit: more here http://go-lang.cat-v.org/organizations-using-go http://go-lang.cat-v.org/organizations-using-go
- ExpiredLink 14y agoApparently Google isn't a heavy Go user and has no plans to become one.
- cleverjake 14y agowhat? could you elaborate?
- ori_b 14y agoThat's not a comment on the technical benefits. It's a comment on turning around battleships. Porting large projects is lots of work, especially when there's plenty of stuff to do that directly impacts the customer. New projects are a different story.
- oconnor0 14y agoAnd it's not even necessarily a good idea to port large projects - completely ignoring the complexity of doing a port while continuing further development and maintenance on an existing product.
- stock_toaster 14y agoyoutube is part of google, and apparently all mysql requests at youtube now go through vitess (or so I read). That strikes me as pretty heavy use. I recall reading somewhere that Go was used for some other internal projects, but never heard what exactly for. So maybe it was just someone talking about some greenfield "20% time" projects or something.
- azernik 14y agoWell, given that YouTube is one of Google's most resource-intensive sites (remember that acquisition back in 2006?), I'd say that alone makes them a pretty heavy user; plus, that's just the bit they've open-sourced. The Go team makes constant reference to assorted internal infrastructure projects for which Google uses Go, but which have not been and which probably never will be publicized.
- duaneb 14y agoThis is flat out wrong.
- drivebyacct2 14y agoAnd... where and how did you draw such a conclusion?
- depr 14y agoin http://www.infoq.com/presentations/High-Availability-at-Heroku http://www.infoq.com/presentations/High-Availability-at-Hero... one of their engineers says they don't actually use Doozer at the moment
- stock_toaster 14y agohuh. Did they mention why? (dont have time to watch it right now)
- stock_toaster 14y agoEnded up watching it, and at the end they said that doozer solves a problem that they don't currently have. He really didn't go into why. Maybe because it was a heroku project he didn't want to talk bad about it? No idea. Interesting talk by the way.