neo4akka
Neo4j Scala client using Akka-Http (by outr)
Elastic4s
Elasticsearch Scala Client - Reactive, Non Blocking, Type Safe, HTTP Client (by Philippus)
Our great sponsors
| neo4akka | Elastic4s | |
|---|---|---|
| - | 2 | |
| 15 | 1,633 | |
| - | - | |
| 0.0 | 8.6 | |
| about 7 years ago | 4 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.
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.
neo4akka
Posts with mentions or reviews of neo4akka.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning neo4akka 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?
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?
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 neo4akka and Elastic4s you can also consider the following projects:
Casbah - Casbah is now officially end-of-life (EOL).
Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala
Scanamo - Simpler DynamoDB access for Scala
ReactiveCouchbase - Play 2 plugin for ReactiveCouchbase
doobie - Functional JDBC layer for Scala.
Shade - Memcached client for Scala
Anorm - The Anorm database library
Salat - Salat is a simple serialization library for case classes.
neotypes - Scala lightweight, type-safe, asynchronous driver for neo4j
scala-sql - scala SQL api