Clickhouse-scala-client vs Elastic4s

Clickhouse-scala-client

Clickhouse Scala Client with Reactive Streams support (by crobox)

Source Code

Suggest alternative

Edit details

Elastic4s

Elasticsearch Scala Client - Reactive, Non Blocking, Type Safe, HTTP Client (by Philippus)

Database Scala ElasticSearch reactive-streams HTTP REST-API Circe

Source Code

Suggest alternative

Edit details

Our great sponsors

InfluxDB - Power Real-Time Data Analytics at Scale

WorkOS - The modern identity platform for B2B SaaS

SaaSHub - Software Alternatives and Reviews

Our great sponsors

Clickhouse-scala-client		Elastic4s
	Project
1	Mentions	2
111	Stars	1,633
0.0%	Growth	-
8.3	Activity	8.6
about 1 month ago	Latest Commit	8 days ago
Scala	Language	Scala
GNU Lesser General Public License v3.0 only	License	Apache License 2.0

The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Clickhouse-scala-client

Posts with mentions or reviews of Clickhouse-scala-client. We have used some of these posts to build our list of alternatives and similar projects.

Anyone using Clickhouse in Scala? What client do you use?
1 project | /r/Clickhouse | 19 Jan 2023

Elastic4s

Posts with mentions or reviews of Elastic4s. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-04.

How to decouple logic from Scala future?
1 project | /r/scala | 14 Dec 2022

Here's an example from a library I've used: https://github.com/sksamuel/elastic4s/blob/master/elastic4s-core/src/main/scala/com/sksamuel/elastic4s/Executor.scala. Then you can provide your own Executor implementation and it will be used instead of the FutureExecutor. You can check out the top level of that repo to see how much complexity this introduces.
Abstraction layers over the various JSON libraries?
4 projects | /r/scala | 4 Mar 2021

Seems like the accepted solution is to have a separate subproject for each of the ~5 major json libraries. For example see elastic4s (elastic4s-jackson, elastic4s-circe, ...) or akka-http-json.

What are some alternatives?

When comparing Clickhouse-scala-client and Elastic4s you can also consider the following projects:

Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala

doobie - Functional JDBC layer for Scala.

ReactiveCouchbase - Play 2 plugin for ReactiveCouchbase

Quill - Compile-time Language Integrated Queries for Scala

Shade - Memcached client for Scala

GCP Datastore Akka Persistence Plugin - akka-persistence-gcp-datastore is a journal and snapshot store plugin for akka-persistence using google cloud firestore in datastore mode.

Salat - Salat is a simple serialization library for case classes.

ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.

Reactive-kafka - Alpakka Kafka connector - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka.

scala-sql - scala SQL api