Casbah is another layer on top of Java driver for MongoDb. Would this reduce performance of queries and updates in MongoDb database in scala projects when using Casbah as opposed to directly using the Java driver?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Casbah is another layer on top of Java driver for MongoDb. Would this reduce performance of queries and updates in MongoDb database in scala projects when using Casbah as opposed to directly using the Java driver?
(I’m the author and maintainer of Casbah)
It should be negligible – I have worked hard over the last 2 years to keep the thickness of any wrapping to the bare minimum.
I’d venture to guess that most users will never begin to experience ANY kind of noticable pain or slowdown as a result of Casbah’s wrapper code over using the straight Java driver.
In many cases because of optimisations Scala is able to make at compile time, I have also observed places where Casbah performs flat out better (especially for iteration type operations) than the Java driver alone.