1) Operationally, HBase is a nightmare whereas FDB is extremely easy to operate.
2) HBase doesn't natively, or efficiently with extensions, support transactions across rows.
3) GC makes HBase performance unpredictable whereas FDB is written in C++.
4) HBase depends on Zookeeper and it is operationally painful to support and we were replacing it with FDB also.
I don't think I will ever again use anything from the Hadoop ecosystem if I can get away with it.
Comments
What were the pro's and con's of using FDB over HBase?
Several things caused us to move off of HBase:
1) Operationally, HBase is a nightmare whereas FDB is extremely easy to operate. 2) HBase doesn't natively, or efficiently with extensions, support transactions across rows. 3) GC makes HBase performance unpredictable whereas FDB is written in C++. 4) HBase depends on Zookeeper and it is operationally painful to support and we were replacing it with FDB also.
I don't think I will ever again use anything from the Hadoop ecosystem if I can get away with it.