{"id":1245,"date":"2010-08-05T07:48:45","date_gmt":"2010-08-05T15:48:45","guid":{"rendered":"http:\/\/blog.mozilla.org\/webdev\/?p=1245"},"modified":"2010-08-05T07:49:22","modified_gmt":"2010-08-05T15:49:22","slug":"the-future-of-crash-reporting","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/webdev\/2010\/08\/05\/the-future-of-crash-reporting\/","title":{"rendered":"The future of crash reporting"},"content":{"rendered":"

In recent blog posts I’ve talked about our plans<\/a> for Socorro<\/a> and our move to HBase<\/a>.<\/p>\n

Today, I’d like to invite community feedback on the draft of our plans for Socorro 2.0<\/a>.\u00a0 In summary, we have been moving our data into HBase, the Hadoop database.\u00a0 In 1.7 we began exclusively using HBase for crash storage.\u00a0 In 1.8 we will move the processors and minidump_stackwalk to Hadoop.<\/p>\n

Here comes the future<\/h3>\n

In 1.9, we will enable pulling data from HBase for the webapp via a web services layer.\u00a0 This layer is also known as\u00a0 “the pythonic middleware layer”.\u00a0 (Nominations for a catchier name are open.\u00a0 My suggestion of calling it “hoopsnake” was not well received.)<\/p>\n

In 2.0 we will expose HBase functionality to the end user.\u00a0 We also have a number of other improvements planned for the 2.x releases, including:<\/p>\n