- [Update 11/28/13] Notes from blog by Jon “Data Driven Disruption at Shuttershock” on what a data products company is
- Data is your product, regardless of what you sell
- Data is your lens into your business – Jon echo’s Peter’s insights viz. invest in data access; feel the pulse of the business & iterate
- Data creates your growth
- Back to the main feature, Peter’s talk
- A very insightful & informative talk by Peter Skomoroch of Linkedin via Zipfian academy
- It is short & succinct, only 37 minutes. I urge all to watch
- The slides of the talk “Developing Data Products” are at slideshare
- Quick Notes:
- A Data Product understands the world through inferential probabilistic models built on data
- So collecting right data through “thoughtful” data design is very important
- The data determines & precedes the feature set & the intelligence of your app
- LinkedIn is a prime example – as they get more data, the app has become more intelligent, intuitive and ultimately more useful
- Offer progressively sophisticated products, leveraging the data & insights, across the different user population segments – customer segmentation & stratification is not just for retail !
- While more data, see “Unreasonable Effectiveness of Data” Distinguished Lecture by Peter Norvig, is good; for complex models, a deep understanding of the models and feature engineering would eventually be necessary (beyond the “black box”)
- Data products about people, are usually complex, in terms of models as well as the data
[Update 12/13/13] Remember, a data product usually has the three layers – Interface, Inference & Intelligence.
The Extremely Large Database/XLDB 2013 Conference & the invited Workshop at Stanford had lots of good speakers and extremely interesting view points. I was able to attend and participate this year.
Previously I wrote two blogs on presentations by Google’s Jeff Dean : and NEA’s Greg Papadopoulos
Here are the highlights from the presentations. Of course, you should read thru all the XLDB 2013 presentation slides.
Last week I attended the XLDB Conference and the invited Workshop at Stanford. I am planning on a series of blogs highlighting the talks. Of course, you should read thru all the XLDB 2013 presentation slides.
NEA’s Greg Papadopoulos had a view point on innovation and startups. Highlights in pictures. Of course, you should read thru the full presentation.
I really liked the “Common Characteristics Of Success”. Golden words indeed !
Came acorss an informative blog on scaling big data – “Built to Scale: How does Impermium process data?” Quick notes from the blog:
Don’t fall in love with a technology so much that you cannot be separated – Be flexible in scaling as you grow
- “Parting is such a sweet sorrow”, but change is an essential component of an infrastructure at scale
- The technology selection and consumption should be a continuous process, introducing new technologies as needed by the growth. I found Impermium’s path from grep to Solr to Elastic Search very illuminating; I have done the same before.
Technology needs are not static
- A corollary of #1 above – Growth on all parts of the stack will not be uniform.
- For example Impermium found scaling challenges in search and they moved to Solr & then to Elastic Search
There are no perfect technologies
- If you are doing interesting work, be ready to tango with open source code. This is essential – I also found this to be true.
- Even if you don’t plan to change the code, many times deep understanding comes from reading the code
Select technologies that you can dance with
- The flip side is that one should select technologies that you are comfortable working under the hood.
- In my case, while I love Erlang, I am not that comfortable with that language. So given a chance, I will go with Java or Scala
Benchmark is nothing but a story in a specific context
- So true. Benchmarks are transitory & personal.
- Understand them, but they need not be true for your transforms, your data model and your processing.
- Benchmark early & benchmark often … with your scenarions, models, transformations, mapreduces & data
Thanks Young for the short but very interesting blog. Keep up the good work …
The Guardian says it all – “Mathematician and daughter of Lord Byron left legacy as role model for young women entering technology careers“.
Ada programming language is interesting. I have developed systems in the Ada language.
In the heels of “All the President’s Data Scientists” another interesting article on the Obama campaign’s cloud infrastructure.
Update : A similar article The Atlantic’s “When the Nerds Go Marching In”
Update : Case Study from New Relic How the Obama For America team improved resilience
- They realized the campaign needed a scalable system “2008 was the ‘Jaws’ moment,” said Obama for America’s Chief Technology Officer Harper Reed. “It was, ‘Oh my God, we’re going to need a bigger boat.”
- They build a single shared data tier with APIs to build lots of interesting applications. “Being able to decouple all the apps from each other has such power; It allowed us to scale each app individually and to share a lot of data between the apps, and it really saved us a lot of time.”
- They leveraged internet architecture “We aggressively stood on the shoulders of giants like Amazon, and used technology that was built by other people,”
- Doesn’t look like they used esoteric technologies. The system is built around Python APIs over RDS, SQS and so forth. Excellent and the fact that the systems can built this way is a testament to the cloud capabilities – IaaS & PaaS
- In short Reed says it all “”When you break it down to programming, we didn’t build a data store or a faster queue. All we did was put these pieces together and arrange them in the right order to give the field organization the tools they needed to do their job. And it worked out. It didn’t hurt that we had a really great candidate and the best ground game that the world has ever seen.”
Another interesting article on how Facebook is preparing for the New Year’s Eve, this time from our own San Jose Mercury News By Mike Swift.
- New Year is one of the busiest times for social network sites as people post pictures & exchange best wishes
CEO Mark Zuckerberg has long been focused on having the digital horsepower to support unbridled growth — are a key reason behind the .. network’s success
- It received > 1 B photo uploads during Haloween 2010
- Since then Facebook added 200 million more members and so New Year Eve 2012 can see more than 1.5 B uploads !
- My favorite quote from the article:
The primary reason Friendster died was because it couldn’t handle the volume of usage it had. … They (Mark,Dustin and Sean) always talked about not wanting to be ‘Friendstered,’ and they meant not being overwhelmed by excess usage that they hadn’t anticipated
- The engineers at Facebook just finished a preflight checklist and are geared up for the scale
- In terms of scale “Facebook now reaches 55 percent of the global Internet audience, according to Internet metrics firm comScore and accounts for one in every seven minutes spent online around the world.”
- From a Big Data perspective, Facebook data has all the essential proprieties viz. Connected & Contextual in addition to large scale – Volume & Velocity (see my earlier blog on big data)
- Facebook has the “Emergency Parachutes” which let the site degrade gracefully (for example display smaller photos when the site is heavily loaded)
- Their infrastructure instrumentation is legendary (for example, the MySQL talk here)
To manage Facebook’s data infrastructure, you kind of need to have this sense of amnesia. Nothing you learned or read about earlier in your career applies here …
And finally, Our New Year Wishes to all readers & well wishers of this blog