Getting Started

Fabric3 is a containerized runtime. Unlike traditional Java runtimes, Fabric3 images are assembled as part of an automated build process. This allows applications to be deployed with just the capabilities they require, resulting in minimal dependencies and optimized operation.

To get setup with Fabric3, clone one of the samples and run the build. The build process will download and assemble a set of fully functional runtimes.

Instructions for installing and running the samples.

Demonstrates how to create, publish, and wire services, process asynchronous events, and use third-party libraries such as Hibernate with Fabric3.

Advanced sample that shows how to build an end-to-end application composed of distributed services.

A Forex trading application that shows how to build low-latency, high-performance services.

Fabric3 {{f3.version}}


Fabric3 provides Gradle and Maven runtime assembly plugins. These plugins enable runtime images to be configured and provisioned as part of an automated build instead of manually downloaded and installed. For details on using the runtime assembly plugin, see the documentation.

GROUP: org.fabric3.gradle
NAME: fabric3-assembly
Version: {{f3.version}}

Fabric3 can be deployed as a standalone server, hosted on Tomcat, or hosted on WebLogic Server. The server and Tomcat distributions contain only the core capabilities needed to run a service cluster. The WebLogic distribution bundles support for WLS JMS, clustering and Web Services. In most cases, you will need to install extension profiles for additional capabilities.

Profiles add a set of features to the Fabric3 runtime. They are installed by unzipping their contents to the runtime extensions directory. Extensions add specific capabilities to the Fabric3 runtime. They are installed by placing the extension archive in the runtime extensions directory.



The CLI is a command line tool for executing management operations against a Fabric3 runtime.

© 2016 Metaform Systems, Inc.