recentpopularlog in


« earlier   
Replacing Sawzall — a case study in domain-specific language migration
Since the logs proxy decouples our data access policy from the programming language used for analysis, individual teams now have more freedom to choose the language that best fits their needs. However, since analysis libraries can often get very complicated, and multiple teams often share common data sources, there is an economy of scale in choosing a common language for most analysis.

At Google, most Sawzall analysis has been replaced by Go. Go has the advantage of being a relatively small language which is easy to learn and integrates well with Google’s production infrastructure. Fast compile times and garbage collection make Go a natural fit for iterative development. To ease the process of migrating from Sawzall, we’ve developed a set of Go libraries that we call Lingo (for Logs in Go). Lingo includes a table aggregation library that brings the powerful features of Sawzall aggregation tables to Go, using reflection to support user-defined types for table keys and values. It also provides default behavior for setting up and running a MapReduce that reads data from the logs proxy. The result is that Lingo analysis code is often as concise and simple as (and sometimes simpler than) the Sawzall equivalent.
mapreduce  go  analytics 
yesterday by janpeuker
Site Kit by Google
I upvoted Site Kit by Google on Product Hunt: Bringing the best of Google tools to WordPress at December 9, 2018 at 12:20AM
Product  Hunt  Analytics  Developer  Tools 
2 days ago by iamthefury
Local marketing tactics are necessary – but the data says they’re not happening
"Despite the embarrassing gaffes we read about from time to time, too many marketers push the same campaigns across global markets. Barb Mosher Zinck says the data on lack of marketing localization is a wake up call."
analytics  planning  and  data  analysis  digital  content  marketing 
3 days ago by jonerp

Copy this bookmark:

to read