All geek questions in one place

For what reasons is it not recommended to use the Thrift API to access Cassandra?

Please calculate the reasons why it is not practical to use the Thrift interface for Cassandra? What are the possible advantages and disadvantages?

+4
source share
2 answers

If you are using raw aprip apis, the cons will be:

  • lack of pooling
  • no monitoring
  • no object oriented interface (not quite true)
  • fault tolerance support
+4
source

To continue the start of Schildmeijer:

  • No batch interface.
  • No chunking get_range_slices () or get_indexed_slices () so you can easily fill in Cassandra
  • Non-string types must be packed in binary strings independently
  • You will probably lose the accuracy of the timestamp.
  • Exception messages are usually useless
  • Thrift is interrupted by default in some languages. For example, see the PHP C Extension.
  • Since the code is generated, it is not intuitive, especially with regard to supercommands, SlicePredicates and batch_mutate ().
  • Schema modification commands do not wait for the coordination of the scheme between all nodes in the cluster
+3
source

Source: https://habr.com/ru/post/1336143/

More articles:


All Articles