Minutes ago Facebook hosted a press conference about their upcoming messaging system, a combination of email and IM
. There weren’t many details about the technical solution, except one slide mentioning that while rebuilding the messaging solution:
- Cassandra was replaced by HBase
- Haystack was extended to be used for message attachments
- Thrift, Zookeeper, memcached are used by the product
Facebook’s choice of #HBase is a validation of a superior scalable architecture. Congrats to the team on some hard, excellent work.
I still need to gather more details about this before commenting if it was a scalability issue or other reasons that led to replacing Cassandra with HBase for Facebook messaging.
Update: more details about the underlying technology of Facebook messaging based on HBase.
Original title and link: Facebook Replacing Cassandra with HBase In New Messaging System (NoSQL databases © myNoSQL)