GETTING STARTED

How to start using the VLINGO/PLATFORM.

The VLINGO/PLATFORM is distributed as a set of libraries and its documentation is available online. The following sections explain how to access both.

To get started quickly with your first example, see the Hello, World! project.

Using Artifacts

The artifacts for the Java Development Kit are available as jar files from three primary public repositories, Bintray, Sonatype, and Maven Central.

Our platform CI builds are performed on Travis-CI, which pushes the successfully built artifacts to Bintray. When we create a release we replicate the Bintray artifacts to Sonatype, which in turn automatically replicates to Maven Central.

We also support daily SNAPSHOT builds on JFrog/Bintray. If you want to use the latest code you may reference it as artifactId-x.y.z-SNAPSHOT. See below for more details.

You may use any number of build tools to retrieve the JAR files that you need for a project. We generally recommend using either Maven or Gradle. You can include the following in your Maven pom.xml file to reference the VLINGO/ACTORS toolkit:

...
<repositories>
<repository>
<id>central</id>
<url>http://repo1.maven.org/maven2/</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>io.vlingo</groupId>
<artifactId>vlingo-actors</artifactId>
<version>x.y.z</version>
<scope>compile</scope>
</dependency>
</dependencies>
...

You may reference SNAPSHOT builds, by including the snapshot repository, as follows.

...
<repositories>
<repository>
# also include normal repository here
</repository>
<repository>
<id>oss-jfrog-snapshot</id>
<url>https://oss.jfrog.org/artifactory/oss-snapshot-local</url>
<releases>
<enabled>false</enabled>
</releases>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>io.vlingo</groupId>
<artifactId>vlingo-actors</artifactId>
<version>1.4.3-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
</dependencies>
...

For use with Gradle you will need something like the following. Refer to the above Maven pom.xml for the location of our snapshots.

dependencies {
compile 'io.vlingo:vlingo-actors:x.y.z'
}
repositories {
jcenter()
// or
mavenCentral()
}

Of course the x.y.z is representative placeholder of the semantic version number of the given artifact. You should examine Bintray for the most recent available daily build artifacts, which are considered snapshots. Stable releases are provided on Sonatype and Maven Central. Generally the tip revision of each JAR file listed in the repository is the one that will work together with all others as a whole platform.

Full open source for the Java platform is available on https://github.com/vlingo. Our baseline JDK is 1.8, but we have successfully used on JDK 1.14. On GitHub you see each of the components that are available, and the above dependency information applies to each of the platform components, but you must supply the actual component name. We maintain version numbers consistent across the entire platform, meaning that if version 1.3.2 applies to vlingo-actors then it also applies to vlingo-lattice and the remaining platform components. The following is an example that uses platform version 1.4.3, but the version should be adjusted to your specific dependencies.

...
<dependencies>
<dependency>
<groupId>io.vlingo</groupId>
<artifactId>vlingo-actors</artifactId>
<version>1.4.3</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>io.vlingo</groupId>
<artifactId>vlingo-http</artifactId>
<version>1.4.3</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>io.vlingo</groupId>
<artifactId>vlingo-symbio</artifactId>
<version>1.4.3</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>io.vlingo</groupId>
<artifactId>vlingo-lattice</artifactId>
<version>1.4.3</version>
<scope>compile</scope>
</dependency>
</dependencies>
...

Support, Training, Consulting, and Project Development

Our VLINGO/PLATFORM developer and production support plans are provided here.

We offer live, virtual training for the VLINGO/PLATFORM. Our team also provides consulting and project development. When you engage with our team you receive the best possible guidance and workforce available for Reactive architecture, software development, and Domain-Driven Design.

Documentation and Examples

You have already found our primary platform documentation. You are reading it.

Our full Javadoc is available here. Individual components are accessible, such as the actors Javadoc. You can even change to the old releases by using the version dropdown. The README.md for each open source artifact also references the current API-based Javadoc. For example, see the vlingo-actors README.md.

Architecture and programming sample projects are available in source form in the vlingo-examples repo. There are several projects. Within them you will find highlights of usage for various platform components.

Public support is available. You may register for access to our public Slack workspace for both Java and .NET.

Follow us on Twitter @vlingo_io.