Description
Vert.x core contains fairly low-level functionality, including support for HTTP, TCP, file system access, and various other features. You can use this directly in your own applications, and it's used by many of the other components of Vert.x.
Vert.x alternatives and similar packages
Based on the "Functional Reactive Programming" category.
Alternatively, view Vert.x alternatives based on common mentions on social networks and blogs.
-
ZIO
ZIO — A type-safe, composable library for async and concurrent programming in Scala -
-
Scala.Rx
An experimental library for Functional Reactive Programming in Scala -
RxScala
RxScala – Reactive Extensions for Scala – a library for composing asynchronous and event-based programs using observable sequences -
SynapseGrid
SynapseGrid is a framework for constructing dynamic low latency data flow systems. -
-
Reactor-Scala-Extensions
A scala extension for Project Reactor's Flux and Mono -
Reactive Collections
A concurrent reactive programming framework.
Less time debugging, more time building
Do you think we are missing an alternative of Vert.x or a related project?
|
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
sponsored
www.sonarlint.org
|
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
Vert.x Core
This is the repository for Vert.x core.
Vert.x core contains fairly low-level functionality, including support for HTTP, TCP, file system access, and various other features. You can use this directly in your own applications, and it's used by many of the other components of Vert.x.
For more information on Vert.x and where Vert.x core fits into the big picture please see the website.
Building Vert.x artifacts
> mvn package
Running tests
Runs the tests
> mvn test
Vert.x supports native transport on BSD and Linux, to run the tests with native transport
> mvn test -PtestNativeTransport
Vert.x supports domain sockets on Linux exclusively, to run the tests with domain sockets
> mvn test -PtestDomainSockets
Vert.x has a few integrations tests that run a differently configured JVM (classpath, system properties, etc....) for ALPN, native and logging
> vertx verify -Dtest=FooTest # FooTest does not exists, its only purpose is to execute no tests during the test phase
Building documentation
> mvn package -Pdocs -DskipTests
Open target/docs/vertx-core/java/index.html with your browser