neotypes alternatives and similar packages
Based on the "Database" category.
Alternatively, view neotypes alternatives based on common mentions on social networks and blogs.
-
Slick
Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala -
-
-
-
PostgreSQL and MySQL async
DISCONTINUED. Async database drivers to talk to PostgreSQL and MySQL in 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. -
scala-redis
A scala library for connecting to a redis server, or a cluster of redis nodes using consistent hashing on the client side. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
scredis
Non-blocking, ultra-fast Scala Redis client built on top of Akka IO, used in production at Livestream -
-
-
Scruid
Scala + Druid: Scruid. A library that allows you to compose queries in Scala, and parse the result back into typesafe classes. -
-
-
-
-
-
-
-
-
-
-
lucene4s
Light-weight convenience wrapper around Lucene to simplify complex tasks and add Scala sugar. -
-
-
-
-
-
-
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. -
InfluxDB – Built for High-Performance Time Series Workloads
Do you think we are missing an alternative of neotypes or a related project?
README
[Logo](site/src/main/resources/microsite/img/neotypes.png)
neotype - a type specimen that is selected subsequent to the description of a species to replace a preexisting type that has been lost or destroyed.
neotypes
:warning: The library is under heavy development. Production use is at your own risk and is not recommended. :warning:
For early adopters:
| Supports Scala 2.12 and 2.13 | |
|---|---|
"io.github.neotypes" %% "neotypes-core" % version |
core functionality. Supports scala.concurrent.Future. |
"io.github.neotypes" %% "neotypes-cats-effect" % version |
cats.effect.Async[F] implementation. |
"io.github.neotypes" %% "neotypes-monix" % version |
monix.eval.Task implementation. |
"io.github.neotypes" %% "neotypes-zio" % version |
zio.Task implementation. |
"io.github.neotypes" %% "neotypes-akka-stream" % version |
result streaming for Akka Streams. |
"io.github.neotypes" %% "neotypes-fs2-stream" % version |
result streaming for FS2. |
"io.github.neotypes" %% "neotypes-monix-stream" % version |
result streaming for Monix Observables. |
"io.github.neotypes" %% "neotypes-zio-stream" % version |
result streaming for ZIO ZStreams. |
"io.github.neotypes" %% "neotypes-refined" % version |
support to insert and retrieve refined values. |
"io.github.neotypes" %% "neotypes-cats-data" % version |
support to insert and retrieve cats.data values. |
"io.github.neotypes" %% "neotypes-enumeratum" % version |
support to insert and retrieve Enumeratum enums. |
Scala lightweight, type-safe, asynchronous driver (not opinionated on side-effect implementation) for neo4j.
- Scala - the driver provides you with support for all standard Scala types without the need to convert Scala <-> Java types back and forth and you can easily add your types.
- Lightweight - the driver depends on
shapelessandneo4j Java driver. - Type-safe - the driver leverages typeclasses to derive all needed conversions at the compile time.
- Asynchronous - the driver sits on top of asynchronous Java driver.
- Not opinionated on side-effect implementation - you can use it with any implementation of side-effects of your chose (scala.Future, cats-effect
IO, Monix Task, etc) by implementing a simple typeclass.
scala.Futureis implemented and comes out of the box.
The project aims to provide seamless integration with most popular scala infrastructures such as lightbend (Akka, Akka-http, Lagom, etc), typelevel (cats, http4s, etc), twitter (finch, etc)...
Resources
Code of Conduct
We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other such characteristics.
Everyone is expected to follow the Scala Code of Conduct when discussing the project on the available communication channels.