Quick Reference

A quick reference to the components that comprise the VLINGO/PLATFORM.

The following components are available for use.

Component

Description

VLINGO/ACTORS

The type-safe Actor Model toolkit for reactive concurrency, scalability, and resiliency using Java and other JVM languages, serving as the foundation for the message-driven platform. Actors are objects, but without direct method invocations. Instead actors send and receive messages asynchronously.

VLINGO/XOOM

The platform adoption accelerator for Java and other JVM languages, including a lightning fast quick boot and quick starter command-line interface and Web-based UI.

VLINGO/HTTP

A reactive HTTP server that provides request-response services that can be embedded into any given service. It is small, fast, and supports fluent APIs that adhere to your DDD Ubiquitous Language as a first-class concern.

VLINGO/LATTICE

Tooling for reactive Domain-Driven Design projects, and featuring highly concurrent models. Includes compute grid, actor/object caching, object spaces, cross-node cluster messaging, object aggregates, state aggregates, event sourced aggregates, CQRS with projections, messaging exchanges, and long-running processes (aka Sagas).

VLINGO/STREAMS

The Reactive Streams implementation for the VLINGO/PLATFORM fully build on the VLINGO/ACTORS reactive and asynchronous foundation.

VLINGO/SCHEMATA

An advanced schema registry provides the means to safely publish standard types that are made available to client services. Provides command-line interface and Web-based UI.

VLINGO/SYMBIO

The reactive, scalable, and resilient CQRS, Event Sourcing, Object, and Key-Value storage, and projection tools for services and applications. With three major persistence types, all based on reactive and actors, there is no strong opinion about a given approach to persistence. Teams are the best to determine their needs, which may be different between Entity types and from one Bounded Context to another. We support a number of cloud and traditional storage engines: DynamoDB, Apache Geode, and various JDBC types.

VLINGO/CLUSTER

The way to scale your services across a number of nodes, whose components can communicate and collaborate with components on any given node.

VLINGO/DIRECTORY

The means by which services register with the system and discover collaborators. It's not a passive "look-up registry." It is a publisher of service availability and access.

VLINGO/COMMON

A small set of reusable components used by multiple platform components. (Don't worry, this is not a catchall.)

VLINGO/WIRE

Wire protocol messaging implementations, such as with full-duplex TCP, UDP multicast, and RSocket, using VLINGO/ACTORS.

VLINGO/AUTH

An identity and access management tool used by the vlingo-platform where data and its use must be secured. Your services may use this facility but are not required to.

VLINGO/TELEMETRY

The reactive metrics collector plugin for the VLINGO/PLATFORM, including support for VLINGO/ACTORS, VLINGO/HTTP, VLINGO/LATTICE, VLINGO/STREAMS, and others.

VLINGO/BUILD

A set of build tool plugins supporting automation for the VLINGO/PLATFORM.

See each of the documents for guidance on how to use of the individual platform components.