Tepkin VS Elastic4s

Compare Tepkin vs Elastic4s and see what are their differences.

Tepkin

By fehmicansaglam

Elastic4s

Elasticsearch Scala Client - Reactive, Non Blocking, Type Safe, HTTP Client (by Philippus)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
Tepkin Elastic4s
- 2
82 1,633
- -
0.0 8.7
- 10 days ago
Scala Scala
- 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.

Tepkin

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

We haven't tracked posts mentioning Tepkin yet.
Tracking mentions began in Dec 2020.

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 Tepkin and Elastic4s you can also consider the following projects:

ReactiveMongo - :leaves: Non-blocking, Reactive MongoDB Driver for Scala

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

Phantom - Schema safe, type-safe, reactive Scala driver for Cassandra/Datastax Enterprise

ReactiveCouchbase - Play 2 plugin for ReactiveCouchbase

Shade - Memcached client for Scala

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

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

ScalaRelational - Type-Safe framework for defining, modifying, and querying SQL databases

doobie - Functional JDBC layer for Scala.

Scanamo - Simpler DynamoDB access for Scala

scala-sql - scala SQL api