Open alfredbaudisch opened 8 years ago
The current design of the client is heavily tied to the Asynchbase HBase driver but the principles are essentially the same:
Feel free to canablise the code as much as you need to put something together. I'd love to work on a driver for Apache Phoenix. It's actually something which could be essential to us at Heroic Labs but I can't promise any kind of timeframe.
I'll look into that, thank you! Btw, Heroic Labs game backend solution uses HBase + diver?
We don't use the current public version of the driver. We do use a lot of the communication code with other Java code which we needed to bridge between Erlang and Java. In fact I should probably see if I can refactor the bridge code into something more generic so it can be shared between projects.
Awesome. I'm also working on a low latency application with Elixir and I'm still deciding between Cassandra and HBase, where what is holding me on the final decision are the Erlang/Elixir connectors. The Cassandra one seems to have performance issues, so I'll probably go with HBase + diver, or I'll try to implement an Apache Phoenix connector with the tips you provided above.
@alfredbaudisch What sort of performance issues have you seen in the Cassandra driver? What sort of latency guarantees do you need with your application? Do you have hard realtime requirements?
I wonder if diver or at least its base code can be used to connect to Apache Phoenix?
Phoenix is basically a JDBC driver, but JDBC support for Erlang/Elixir seems lacking.