5 ms·
Google transfers 1.2 EB of data every day using Effingo
- Ecco 2y agoI’m not quite sure how I feel about that tool’s name. I like that it’s a slang but aren’t they overdoing it? Or am I misunderstanding the whole thing?
- jganetsk 2y agoI know the Effingo team at Google. It comes from Latin https://en.wiktionary.org/wiki/effingo#Latin https://en.wiktionary.org/wiki/effingo#Latin
- dekhn 2y agothat doesn't stop the team from occasionally pronouncing it as "effing go"
- cathalc 2y agoAs someone who's never even seen the term written before, that's exactly how I pronounced it..
- mrinfinitiesx 2y agoyeah like the 'big falcon rocket' -> big fucking rocket effing go for me too
- mike503 2y agoYeah. F'ing go! is what I assumed.
- the-rc 2y agoBack when it was introduced as a replacement for Transfer Service 15 years ago or so, the mention of the Latin etymology was always accompanied by a wink...
- deleted 2y ago[deleted]
- nottorp 2y agoGreat, another service that ex googlers will advocate for at startups with 10 customers and 2 Mb/day transfers. Because it scales!
- xnx 2y agoI'm not sure ex Googlers are even necessary for ill suited technologies to be used. There definitely weren't enough ex-Googlers to explain the spread of microservices or NoSQL. Reading about it on Hacker News might be enough.
- pjmlp 2y agoMicroservices are just SUN RPC, CORBA, DCOM, EJBs, .NET Remoting, SOA, WCF, rebranded for a newer generation, which apparently hasn't learnt much about them. Hence now the modular monolith hype, as they rediscover programming languages have modules, and placing a network in the middle doesn't sort out spaghetti dependencies!
- thecleaner 2y agoIts applicable if the services have different teams and different infra requirements. Its hard to create a ton of sphaghetti when integration is atleast a network hop away. There's some friction to being dependent on too much stuff.
- liveoneggs 2y agohttps://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law
- pjmlp 2y agoTell me you never wrote a call graph across distributed services architecture, without telling me. At least now Open Telemetry based tools can render those in beautiful ways.
- nottorp 2y ago
- the_broken 2y agoThe ACM SIGCOMM paper is here - https://dl.acm.org/doi/10.1145/3651890.3672262 https://dl.acm.org/doi/10.1145/3651890.3672262 It is open access, so you should be able to see the PDF. There is a youtube video summarizing the main points: https://www.youtube.com/watch?v=hBME9Q6RPZ8 https://www.youtube.com/watch?v=hBME9Q6RPZ8.
- amluto 2y ago1.2 EB is 1.288e9 GB. The lowest listed price for cross-region traffic at Google is 0.2c / GB. That’s almost $2.6M per day to run this program — actually, more, because a bunch of the traffic surely goes outside North America! Google can afford that, but most companies can’t. I’m being sarcastic, if this wasn’t obvious.
- remram 2y ago1.2 EB is 1.2e9 GB
- amluto 2y agoI was assuming that these were actually EiB and GiB. The egress prices are documented as such, and networking is usually counted in powers of 1024.
- remram 2y agoI mean, possibly. Networking is usually counted in bits though. I wish there was a way to signify "I know about EiB I do mean EB". If you write EiB, there is no chance you meant EB, but the other way around is always ambiguous...
- pxx 2y agoI spell out "trillion / quadrillion / quintillion bytes" for base-10 terabyte, petabyte, exabyte when the distinction is important. they're also unlikely to be confused with long-scale.
- amluto 2y agoEvery Google investor should care deeply about that factor of 1.024^3 when evaluating the cost of running this amazing money sink. Oh wait, maybe the endpoints are in the special list of Google endpoints to which traffic is zero rated. :)
- watercool 2y ago[dead]
- deleted 2y ago[deleted]
- hulitu 2y ago> Google transfers 1.2 EB of data every day using Effingo So that's how much data they collect from their users every day. /s
- zjvkwbc986 2y agoDavid Ziegler was the original designer and engineer who actually built effingo with all kind of headwings. It seems rather unfortunate he is merely mentioned as one of many who worked on it. That's probably why google hasn't really done any new groundbreaking system for the past 10 years.