HBase @ Facebook
Kannan Muthukkaruppan overviews HBase, explaining what Facebook Messages is and why they chose HBase to implement it, their contribution to HBase, and what they plan to use it for in the future.
Kannan Muthukkaruppan overviews HBase, explaining what Facebook Messages is and why they chose HBase to implement it, their contribution to HBase, and what they plan to use it for in the future.
Google, Facebook and other companies operating totally 21 Social Networking websites are facing criminal proceedings in an Indian Court, over objectionable content accessible through the websites. A High Court has warned that the sites can face a ban in India unless they screen content. Is the growing flux of regulations surrounding social media a risk for businesses investing in social?
Steve Jones, Global Head of Master Data Management at Capgemini and a SOA practitioner, thinks that Facebook's recent announcement about deprecating their REST API in favour of what they call a 'Graph API', is actually a good step for REST in that it may offer a way to cut through the "religious fundamentalism" that often surrounds it.
Following on from the recent release of Spring Social, InfoQ caught up with Craig Walls, lead of the project. The interview covered the current state of the project, as well as the community involvement since its release.
Customers use a wide variety of technologies for communication and expect the companies they deal with to do the same. This means the same message may need to be sent to a mailing list, a Twitter account, an IRC channel, and a Facebook page. To make this easier, developers can use the Broadcast library for Ruby or its .NET clone, nBroadcast.
A number of announcements around open hardware specifications and open source cloud infrastructure and platform software solutions by collaborators in the OpenStack initiative were made in the past 2 weeks. How does all of them stack up together?

Nick Schrock presents how Facebook’s code evolved over time, explaining some new constructs – fbobjects, Preparables, Ents - introduced to address the complexities of a large social graph.
Jason Sobel presents the evolution of Facebook’s infrastructure over time, from the original LAMP stack to the present multi-datacenter configuration, the challenges faced and plans for the future.

Beside presenting the overall Facebook architecture and scaling solutions used, Aditya Agarwal talks about the iterative process of constantly improving the site, making sure to avoid over-engineering and adapting along the way by dropping solutions that worked in the past but are no longer useful. The last part of the session was dedicated to answering questions from the audience.

Robert Johnson discusses Facebook’s approach to scalability issues resulting from a large growth of the user base. He talks about: why one needs to prepare for horizontal and not vertical scalability, very short release cycles which are better because they introduce fewer bugs, the need to streamline to deploying process for short release cycles, and making the entire process faster every day.
In this interview Jez Humble discusses the concept of continuous delivery, which implies that software should always be production ready throughout its lifecycle. That means that every build could be released into production and run effectively. Continuous delivery involves build and deployment automation, continuous integration, test automation, managing infrastructure and environments and more.