Google Router Rumors 267
An anonymous reader writes "There's a new rumor that Google is developing its own router. The company won't comment on the story, but it's been in the hardware business for a while and expanded its presence with Android. If Larry Ellison can go halvsies with HP on a server, then Eric Schmidt should certainly be able to make Cisco nervous."
one more reason... (Score:5, Funny)
Re: (Score:3, Insightful)
why procrastinate? the CCNA really isn't that hard of a cert to get.. the NP's are difficult.. and no mater what google does.. if you have an IE you will be able to find a job
Re:one more reason... (Score:4, Funny)
the CCNA really isn't that hard of a cert to get..
It took me many months to pass my Can't Configure Network Anymore (CCNA) exam, you insensitive clod!
I'm planning to take Can't Control Network Protocols (CCNP) at age 50, and
Can't Configure It Effectively (CCIE) at age 75.
See definitions [cnp-wireless.com].
All that I need now is google underwear! (Score:5, Funny)
All I need now is google underwear that twitters for me with real time gps tracking so I know where I've been.
Re:All that I need now is google underwear! (Score:5, Funny)
Do you really want to wear underwear that's in perpetual beta? Ouch!
Re: (Score:2)
Bricks and pants..
Re:All that I need now is google underwear! (Score:5, Interesting)
Don't hold your breath, have you seen the Google Appliance [google.com]?
Re: (Score:2)
I like the LaCie drives [lacie.com].
Old news - Google broadband in 2007 (Score:4, Funny)
This is old news and was announced almost two years ago http://www.google.com/tisp/ [google.com]
Re: (Score:3, Interesting)
Re:All that I need now is google underwear! (Score:5, Funny)
I loved getting the big yellow Google box at my last job. And it came with a black Google t-shirt too! I had one job setting up a NOC for sextracker.com back in the day. I ordered 10,000ft of Cat5 in hot pink. Made it easy to find my stuff in the colo.
Re: (Score:2)
Come to think of it the jr. neteng I hired there now is a Sr. neteng at Google. Hmmm..
Re:All that I need now is google underwear! (Score:4, Funny)
serverbay watch
In My Opinion, Cisco Should Be Worried (Score:5, Interesting)
I seem to remember rumors of them building their own insane (10 GbE) hardware switches [nyquistcapital.com]. And I don't think that's hard to imagine as nothing on the market at the time could possibly meet their needs.
... like many claims they could not be operating on TCP/IP stacks on the inside. Because it's such a resource hog in some respects but that's irrelevant--I'm certain they can apply some of their ideas universally. I would put my money on them being the leader in research on networks and network theory ... probably past Cisco even (although behind the NSA as no one's ever sure about those guys). I feel that networking is so closely tied to their bread and butter search application that they should be dumping huge R&D into that field. I can't offer proof but it certainly makes sense to me.
Of course, there's a lot of questions that remain to be answered
And all I can say is that it's about time someone put pressure on the home & enterprise networking hardware companies. What a stagnant squabbling market that has become.
Re:In My Opinion, Cisco Should Be Worried (Score:5, Insightful)
And all I can say is that it's about time someone put pressure on the home & enterprise networking hardware companies. What a stagnant squabbling market that has become.
The fine article seems to be down, so I can't tell what it claims. But I suppose the "Google Router", if it exists, will put an end to Juniper and Cisco in the same way as Bigtable does for Oracle, PostgreSQL etc.: it doesn't because the technology is so fundamental for Google's success that they simply don't share it.
Re:In My Opinion, Cisco Should Be Worried (Score:5, Funny)
Reading TFA, It is basically saying that the loss of Google alone as a customer would doom Juniper. It doesn't matter if Google shares its technology or not as far as Juniper is concerned.
Re: (Score:2)
Re:In My Opinion, Cisco Should Be Worried (Score:5, Interesting)
Isn't Juniper's business plan to install FreeBSD on cheap embedded hardware and pretend that it's special-secret-proprietary-magic? I wouldn't be surprised if Google could undercut them, for in-house use at the very least.
This is not really true. On the higher end Juniper boxes, while the control plane is running FreeBSD, the real work is done on the forwarding plane which is comprised of custom ASICs. You can't route at an enterprise or carrier level using commodity hardware.
If Google is building an in-house router, it's down to the hardware design level. Either they're developing their own ASICs (plausible) or they're using merchant silicon (even more plausible) and rolling their own OS and chassis.
Re: (Score:3, Informative)
Isn't Juniper's business plan to install FreeBSD on cheap embedded hardware and pretend that it's special-secret-proprietary-magic? I wouldn't be surprised if Google could undercut them, for in-house use at the very least.
Do you really think that FreeBSD has anything to do with routing packets and the other functionality on Juniper routers? In fact your comment suggests that you could put FreeBSD on the same hardware and acheive equivalent levels of features and performance, which really is incredibly uninformed.
Re: (Score:2, Insightful)
No it won't.
BigTable and relational DBMS are very different - neither will replace the other in the near future.
Custom hardware at Google isn't unheard of. TFA doesn't state if the router is to be sold as a competing product or if it's just going to be used internally. It's just a rumor, don't hold your breath
Re:In My Opinion, Cisco Should Be Worried (Score:5, Interesting)
"And all I can say is that it's about time someone put pressure on the home & enterprise networking hardware companies. What a stagnant squabbling market that has become."
If they do get into network tech, I seriously hope they release some home routers. I'm probably not the only one tired of having to reboot home routers every so often, especially with multiple people connected and having their wireless connection suddenly drop.
Re:In My Opinion, Cisco Should Be Worried (Score:5, Insightful)
Simple solution -- quit buying crappy (i.e. Linksys) routers. I've used Netgear routers for 10+ years, and have never had to reboot or replace a broken router.
Re:In My Opinion, Cisco Should Be Worried (Score:5, Interesting)
Mostly seems to stem from power fluctuations, google search [google.co.uk] brings up nothing specific, but anecdotal evidence on my part and some customers seem to agree. Anyone else have this?
Re: (Score:2)
Re: (Score:2)
And OP also seems to have trouble with a router he's using at home.
Re: (Score:2)
My wrt56g sucked so hard out of the box (5-10 seconds per domain lookup, and it happened _every time_ I loaded a page) that I put DD-WRT on it. I have always had it on the UPS, so I can't comment on any additional stability.
DD-WRT is awesome. It fixed my router and made it better than it was before!
Re:In My Opinion, Cisco Should Be Worried (Score:5, Informative)
Tomato is good, too. I found Tomato to be less buggy and more responsive and DD-WRT -- and believe me, I was fanatical about DD-WRT. I used it for years before trying Tomato.
Re: (Score:2)
Simple solution -- quit buying crappy (i.e. Linksys) routers.
I've been using a Linksys WRT54 for 2 years, now, and have never had any problems with it. Before that, I used a d-Link DLG624 for 2 years and had frequent loss of connection requiring rebooting the router.
Re: (Score:2)
Linksys may be crappy, but at least you can install a community-supported variant of Linux on many of their router models.
Netgear is, in my experience, even crappier (as evidenced by how flaky my WPN824 was), and there are very few choices as far as open source alternative firmwares for Netgear routers. They marketed an "open source" router for a while, but I could not find a single instance of third party firmware for that router.
Sadly, Buffalo Technology refused to give into patent trolls and so their wi
Re:In My Opinion, Cisco Should Be Worried (Score:4, Interesting)
There are plenty of options for robust routers, even smallish ones; but the cost of entry will be 2 or 3 times higher than the cheapies.
Re:In My Opinion, Cisco Should Be Worried (Score:4, Informative)
PC Engines (Score:2)
PC Engines [pcengines.ch] are another option.
Meh, the software catalog was always a bit limited. I mean, OK, they had Bonk's Adventure - but how does that measure up against the likes of Sonic the Hedgehog, Super Mario Brothers, or Rockman?
Re:In My Opinion, Cisco Should Be Worried (Score:5, Funny)
although behind the NSA as no one's ever sure about those guys
The real secret of the NSA is that they've got a zombie Alan Turing kept functioning on a combination of nutrient bath and Jeff Stryker porn.
Re: (Score:3, Funny)
They are using OpenMPI with a custom transport over Gig10e hardware. For their switching they have basically gone to a stacked of switching fabrics. It is pretty much a 3D fabric they call a bolt. :)
Of course I am making all of this up but dang it sounds good
You mean Juniper should be worried (Score:5, Insightful)
Just like with the 10G switches, this has all the earmarks of something for purely internal use rather than something they're planning to sell. That means their current vendor, which is Juniper according to TFA, loses Google as a customer, but that's about it.
If anything, Cisco should be happy that their competitor is losing business.
Re: (Score:2)
Cisco should be happy that they came in third and not second?
Re: (Score:3, Funny)
I for one welcome my new free, yet perpetually in beta router.
All you have to do is let them monitor all of the traffic that goes through them so they can data mine it for useful but anonymous markeing information.
If they do (Score:5, Insightful)
I hope they include sensible and up-to-date standards and protocols. I'm thinking about the possibilities of the interface of the tomato firmware and importantly, inclusion of ipv6 support. If we want this to happen in this generation we need to get software support on at least basic networking devices(thinking of routers and OSes).
Re:If they do (Score:4, Interesting)
I really hope they throw in IPv6. There are no consumer-level routers available with IPv6 support; it's been driving me crazy. Everyone will probably be forced to buy new routers in a few years anyway.
With that said, I think Google is probably developing a router for their own in-house use. I have doubts this will actually hit the consumer market.
Re:If they do (Score:5, Informative)
The Apple Airport Express and Airport Extreme routers support IPv6, although there's a bug in the latest firmware for doing configured tunnels.
Re: (Score:2)
Re: (Score:2)
As far as I know, yes it can be flashed. I believe that consumer hardware can be flashed to support ipv6. Unfortunately that is not enough since you need to include ipv6 support in all software that likes to use the internet. We still have a long way to go but consumergrade hardware with ipv6 support would be a good start.
Re: (Score:2)
Re: (Score:3, Interesting)
The lines between software and hardware are actually really blurry. Most NICs, for example, have hardware which assists in manipulating packets--anything from simply managing the checksums to VLAN tagging. Some cards even come with prioritization in the ASIC. Then you get highly programmable NICs which basically include an FPGA and a programming interface. With these, you can implement a somewhat arbitrary portion of the TCP/IP stack in the FPGA.
"But it's still softare!" you may cry. Well, maybe. But
Re: (Score:2)
Re: (Score:3, Informative)
It's interesting that Apple OSX has supported IPv6 for a while (probably a side-effect from using BSD) and Apple routers (Airport Extreme) supports IPv6 and (if I remember the specs right) tunneling IPv6 over IPv4 out of the box and enabled.
While that does not represent the vast majority of the computers/home routers in use, this does show that some companies are trying to start the trend.
Re: (Score:2)
Google was just trying to save money (Score:5, Insightful)
The problem is that Google develops tech internally that is extremely good at solving their problems, but they don't always apply well outside of Google. Protocol Buffers aren't exactly obsoleting XML and from all indications they probably never will. The Google router will probably be super fast and simple, but lack a whole bunch of the more obscure features. The problem is that there's someone out there for each one of those obscure features, and if you don't support it your product won't even make it in the door. This is a problem Juniper runs into a lot, they have good and fast hardware, but the only thing it does is route.
In fact the article points out that Google's router is most likely to compete directly with Juniper instead of Cisco.
Re: (Score:2, Insightful)
Re:Google was just trying to save money (Score:5, Interesting)
Too right on this point. I used to work for Cisco, and was always amazed at the number of bugs filed by customers around really obscure and esoteric features. Every one of those obscure features is in IOS because somebody (usually somebody big with deep pockets) is still using it... Even simple things like OSPF timers - they all have to be adjustable, because some big shop has decided that they can squeeze an extra .1% of bandwidth out of their pipes by fiddling with those timers - and if your new box requires them to reconfigure their whole network to standards (or worse yet, to the values that worked best in Google's network) they're not going to be very interested...
Re: (Score:2, Interesting)
> ...it probably isn't surprising that they wanted to develop their own routers from
> scratch instead of paying through the nose for Cisco or Juniper devices, especially
> since they needed hundreds or thousands of them and really don't want to have to pay
> for support contracts.
When you buy thousands of routers you get them customized to your exact needs and you get whatever support arrangement you desire including complete drawings and source code.
Re:Google was just trying to save money (Score:4, Insightful)
When you buy thousands of routers you get them customized to your exact needs and you get whatever support arrangement you desire including complete drawings and source code.
Evidence? I've never heard of Cisco/Juniper/etc. offering this.
Re: (Score:3, Informative)
This sort of thing doesn't get offered, it is thrown in or dragged out as a sweetener for a humungeous order. And it is usually covered by a confidentiality clause because they don't want to be forced to offer it to the next, merely large, customer. But if you are placing an order which represents a serious fraction of quarter's output, you can get a lot thrown in - espexially if it doesn't actually cost anything to provide.
Though this would be a problem rather than a benefit for Google. They would have to
Re: (Score:3, Informative)
When you buy thousands of routers you get them customized to your exact needs and you get whatever support arrangement you desire including complete drawings and source code.
Do you think that companies like AT&T who have 10s of thousands of switches/routers get IOS source code from Cisco? Do you think that ATT would waste resources on having people "reviewing IOS source code"?
You get features/enhancements added because you buy so much, but you don't get schematics and source code...
Comment removed (Score:3, Interesting)
Re: (Score:2)
What has Android done for phones?
What is Android trying to do?
Android (Score:4, Insightful)
2. it's open source
3. it's open source
and probably some other reasons too [iphone-ipod.org].
Re: (Score:2)
How does open source do anything for phones?
(Hint: It doesn't! 99.9% of people buying phones don't give a shit about open source, and never will.)
Re: (Score:2)
It's for the users who appreciate it, like when Linksys WRT54G were 'hacked', it meant a lot to some people [wikipedia.org]. Isn't openness a good thing? Presumably that's why so many people [yellowsn0w.com] work on opening the iPhone to better freedom and development.
Sure it's not for everyone, but openness, competition and freedom is usually considered a good thing!
Re: (Score:2)
I can see it now... (Score:5, Funny)
Re:I can see it now... (Score:5, Funny)
I'd be rather surprised if "ping 192.168.1.20" resulted in trying to ping 192.168.1.200. Might want to check your network settings or something.
Re:I can see it now... (Score:5, Funny)
I'd be rather surprised if "ping 192.168.1.20" resulted in trying to ping 192.168.1.200. Might want to check your network settings or something.
That was the auto-complete feature. :D
Re: (Score:2)
funniest damned thing I've read in a long time.
well done.
IPv6? (Score:2)
Hopefully they will get IPv6 in as a standard feature. I get annoyed at being told I need to start getting ready for IPv6, only to find out that the Apple Airport is more or less the only one offering this feature out of the box.
doing it right (Score:3, Interesting)
1) raise the barrier to entry, no point issuing a device that anyone could make with Linux and a '386. Also, many cisco routers (eg. the 1800 series) genuinely represent value for money.
2) Provide good quality support.
So to raise the barrier to entry, it has to be a pretty special product, maybe doing the most useful 80% of what a cisco does flawlessly and improving upon cisco in come other areas (ones I can think off of the top of my head are ease of deployment and virtualization (vrf)).
The other reason people insist on Cisco, even when there are other cheaper options, is that they believe Cisco support their product well with training and technical support. This in my experience is an illusion. By and large the Cisco TAC is awful and maintaining certification is expensive and time consuming and the training materials are riddled with misprints, bugs and corporate "best practices" that are self-serving to Cisco.
So Google have a huge hill to climb, but I'm sure that it can be done in the space of a couple of years.
Re: (Score:3, Insightful)
I don't think it's that huge of a hill for Google. Remember the iPod? Came from nowhere. Google has a pretty good brand name. If their product slips out and performs well, there is no reason to believe that it won't be accepted as fast and widely as other Google products.
Re: (Score:3, Insightful)
Yes, but Apple had an incentive and a business model that consumers could live with. I'm not sure that you can say the same thing for a Google router. There's no particular business model other than spying on the owner and I doubt that many people would go along with that without something in it for them.
Re: (Score:2, Insightful)
You are aware of the idea of selling routers, right?
Re: (Score:2)
TFA says Juniper is doomed. Not so fast. (Score:5, Informative)
Nothing to see here. Move along.
Re:TFA says Juniper is doomed. Not so fast. (Score:5, Informative)
Of course Google would not waste time developing their own ASICs. Companies like Marvell, Broadcom, and Dune offer plenty to choose from, and companies such as FDRY and JNPR already use these to build their own offerings.
It only makes sense for Google to use the building blocks to make a device that meets their specific needs.
Mod AC Informative (Score:2, Interesting)
Post is exactly right. The ASICs are already out there and in use by pretty much everyone for their COTS routers.
When one gets into the carrier-scale equipment I don't have a clue how that stuff goes. But I've seen enough low-end ( $10,000) routers taken apart to know that AC's comments are accurate.
Re: (Score:2)
Re:TFA says Juniper is doomed. Not so fast. (Score:5, Interesting)
Or Google could buy Juniper. Let the rumor drive down the stock and pick them up at fire sale prices.
Re:TFA says Juniper is doomed. Not so fast. (Score:5, Insightful)
That really depends. For smart companies, they've sufficiently diversified their client base such that the loss of one will hurt but not cripple. Some clients, however, just become so damn big and a company simply can't get enough other clients or the increase the volume from the other existing clients high enough to balance against that one mega-client. Once one client represents a massive percentage of your revenue and the loss of that client would force you into immediate emergency restructuring in the hopes of survival, then yes, one client a demise can potentially make.
Re:TFA says Juniper is doomed. Not so fast. (Score:5, Interesting)
Re: (Score:3, Insightful)
The questions really are: how many different types of ASICs and boards are in those routers plus how many of the ASICs cannot be r
Re: (Score:2)
It is clear that Google already has expertise in chip design
What expertise have they demonstrated? Android doesn't mean much. That means they could design a router? Now creating a router that only supports a couple of protocols that they specifically need as opposed to the general purpose routers that require IOS/JUNOS and all the features they support.
However if Cisco can go out and make servers, than I'm sure google could hire enough people to build a router.
Re: (Score:2)
TFA says that Juniper is doomed because Google is getting ready to switch to their own in-house brand of routers. I find this difficult to believe for several reasons. One is that even if Google is Juniper's biggest customer, one customer does not a demise make -- Juniper has many other customers...
Agreed. I worked in the routing industry and Juniper has plenty of loyal customers yet.
But there are far more practical reasons. Routers contain a lot of specialized hardware designed for rapid switching of packets.
I'm not as firm on this one. There are a number of generic switching hardware manufacturers out there with nice platforms upon which anyone can build a Linux or NetBSD device with a little work. Also, you can get a lot out of many smaller devices working as a mesh when you factor in the cost of a lot of little generic boxes. It would not be so hard to start with switches and then start replacing routing hardware heading t
Re: (Score:2)
Well, as someone working in the auto industry, I've seen first hand how this is not true. We have many suppliers that are in trouble simply because Ford or GM has scaled back their production so much. I work for an automaker that still is profitable.. but we're getting hit hard because of supplier closings.
For example, if Supplier X makes 1000 widgets per day, they have the employees, the equipment, and the building to do it efficiently and cost effectively. If,d
No Thanks. (Score:5, Funny)
My router works fine, and I don't have Google stealing all of my LAN packets and serving me ads.
A fucking grouter had better make me warm delicious waffles if they want me to buy it. Even then, I'd only use it to make waffles.
And now I'm off to amazon to look for a waffle maker.
Re: (Score:2)
No comment, eh.... (Score:2)
How fucking UGLY would that be? (Score:2, Funny)
BARF!!!
Oh, I'm sure it'll work great - but hide that bitch in the rear of your rack space, that's for sure.
Not in "hardware business," won't sell routers (Score:5, Insightful)
Everybody seems to be assuming that these new routers will be for sale. That's obviously not going to happen — there just isn't room in the marketplace for a new player, even if that player is Google. Breaking into a new hardware marketplace is hard. You have to develop sales channels, create a hardware support organization, set up an operations organization to manage production, etc. etc.
I know about these things because for the last couple of years my job has been to document some of Sun's hardware products. Before that I mostly documented software, and the shear complexity of designing, building, distributing, selling and supporting actual physical products still boggles my mind. At product team meetings I sometimes feel at sea, even though the technical concepts I have to deal with are actually much simpler than those I faced when I was on software product teams. The logistics are just mind boggling.
Google isn't set up to be "in the hardware business". They make their own servers because there are no manufacturers that are able to meet their specialized needs. Now they seem to have decided that their routers also require specialized in-house designs. They haven't tried to sell these servers to other companies, and they won't try to sell their routers. Even if they could hope to compete, it would mean building up the kind of technical bureaucracy that Google's top echelon has no interest in managing.
Hell, they don't really have a proper bureaucracy for the much simpler job of creating and distributing their software products. If they actually charged money for most of them, they'd be trouble.
And Android? How does Android count as being "in the hardware business"? Is Google selling a cell phone I haven't heard about?
Re: (Score:2)
I think you're mostly right: Google will never sell specialized router hardware.
However, I doubt that Google uses special router hardware even for themselves. I'd bet that a Google router platform would be based on a commodity PC with a few PCI Express gigabit ethernet adapters, installed with open-source routing software. Google likely has no interest in supporting the billion weird or legacy options that are present in the Juniper and Cisco products, so it's able to make a commodity unit that is a te
Re: (Score:2)
Check the Google search appliance, sure it's just a standard 1U machine loaded with their software, but say they did the same with more networking ports and bundled it with some of their cool routing/loadbalancing stuff?
Re: (Score:2)
I'd bet that a Google router platform would be based on a commodity PC with a few PCI Express gigabit ethernet adapters, installed with open-source routing software.
I'm not an expert on this, but it's my understanding that a cost-efficient router is very different from a commodity system. Any computer can work as a router, but to route a lot of traffic cheaply you need specialized hardware. That's why the dominant player in the router marketplace is Cisco: they were the first to realize that there was a market niche that was never going to be filled by general-purpose computers.
If ordinary data centers with a few thousand servers don't find it cost effective to use gen
Re:Not in "hardware business," won't sell routers (Score:4, Interesting)
Huh? Gigabit ethernet is "hardly relevant"? What world are you living on?
The world of high performance networking. GigE is "hardly relevant" to the notion of building your own router because it's now ubiquitous. Everyone can do GigE and cheaply. There's really no money to be saved by building your own GigE router. 10 GigE is what everyone needs. If Google is building any hardware, rest assured it's for non-blocking 10 GigE port density and price.
Well, it's hard to refute a statement that uses marketing-speak like "enterprise-level pps performance". A commodity PC can achieve gigabit throughput, though
It's not marketing-speak. Poor packets per second performance is a common problem with networking gear. In actuality, it's a very normal "market-speak" thing to quote Gbps numbers without specifying packet size (like you did). Do you know the difference between being able to forward 64 byte packets at GigE and 1500 byte packets at GigE? Hint: small frames/packets can often kill commodity PC routers. So saying something "can achieve 2-3 Gbps" is meaningless if you don't specify a packet size.
And to be clear, Vyatta might very well be able to do 2-3 Gbps with 64 byte packets. Google really wouldn't care though, as 2-3 Gbps is nothing.
Re: (Score:3, Interesting)
Of course it's with 64-byte packets: that's the common lingo of network hardware manufacturers. You can find similar throughput measurements on every piece of Cisco or Juniper equipment. Anyone that quotes bandwidth throughput in passing will use the 64-byte figure, since it's always the highest one.
Um. No. It's not the highest one. It's typically the lowest one. As I said before, small packets kill PC based routers.
Vyatt'a own paper [vyatta.com] shows it.
Am I then only one who... (Score:5, Insightful)
Am I the only one who read this and thought, "Hmmm, it must be time for Google to renew their support contracts with Juniper.".
"leak" a rumor about no longer needing Juniper, and watch juniper lower their support rates.
CISCO has nothing to fear (Score:3, Interesting)
Why go bringing CISCO into this. Apart from creating products people want to use (gmail, search, etc..) google has two main focuses: building a back end able to efficiently run those applications and ensuring the consumer has easy access to those services.
Android and google's actions in the spectrum market weren't made just to fuck around with products outside their core competencies. They were strategic moves made to ensure that customers on mobile devices didn't end up directed away from google products by someone controlling the network or providing the handset.
Similarly google isn't about to start competing in the router market just for kicks. It's outside of their core competencies and the potential for profit simply wouldn't justify the resource expenditure.
Likely google is working on a custom router to help make their backend more efficient. To take an educated guess I would imagine that they want to build in intelligent load balancing into their routers. In other words have the routers maintain information about where certain kinds of data live and/or what machines are heavily loaded and then intelligently send requests for computations to lightly loaded nodes near the data. They might also want to simply build in custom handling of packets for things like GFS.
Not only will google not bother to compete in the router market but I suspect they won't even allow the technology they use for this to escape the company. After all most of the people who would benefit from this kind of optimization are their direct competitors.
googlefood (Score:2)
Re: (Score:2)
Those are the wrong questions, Google doesn't have a business model. They've been getting better, but the R&D has been all over the map and much of it doesn't have a prospective positive cashflow until after release. I'm not saying that all research needs to have an obvious way of marketing it, but a business shouldn't be buying out other businesses that lack a business model.
As a business they've been surviving largely upon largesse and a DoJ that doesn't believe in regulation. At some point they'll ha
Re: (Score:2)
it doesn't contribute to google's business model, the rumor speculates that this is a bit like big table, and the rest of google's internal stuff. Basically they can't buy routers to handle internal traffic that satisfy their needs, so they are building their own for use in their data centers (ala big table, where they built a db technology rather than use oracle, or some other existing tech)
Re: (Score:3, Informative)
It's an awful summary. Google isn't dumb enough to go compete in the router market. They are likely creating optimized routers to service their own backend.
Don't you remember this was the same thing that happened when information on GFS leaked or the custom OS versions they use in their data center. People hyped it up as if google was going to take on MS in the OS arena.
Re: (Score:2)
Push button BGP configs? So that's why I'm looking for work!
Re: (Score:2)
I agree, but for reference, the flu search thing is child's play. Also, "predict" isn't really accurate here. What they mean is "identify."
Re:Vyatta anyone? (Score:5, Informative)
I can't believe nobody has made mention of Vyatta. It's an excellent appliance-like distro based on, I believe, Debian.
It's not mentioned because it's not even remotely relevant to the discussion.
All the bells and whistles you'd expect from a high-end device at a fraction (by which I mean ~1/3) of the cost relative to a Cisco purchase.
Including bells and whistles like custom ASICs and switching fabrics? Oh, wait, it doesn't have those. Nothing about Vyatta is "high-end." It is, however, a viable alternative at the very low-end.