...
- Unlike Java EE app servers, Fabric3 is designed with integration in mind to enable service-based as opposed to siloed autonomous (and often monolithic) applications. Fabric3 assembles composite is used to assemble applications from distributed services that may be hosted in a vairety of disparate systems. loosely-coupled distributed services.
- Dependency injection frameworks such as Spring and Guice assemble local application components; Fabric3 extends assembly from local to distributed services.
- Unlike Enterprise Service Buses (ESB), Fabric3 is not based on a proprietary programming and integration model that routes sends all communication through a messaging abstractionrouting and transformation framework. Instead, Fabric3 relies on the SCA standards standards such as OASIS SCA and JAX-RS and open protocols such as ZeroMQ to wire application components directly or through typed channels without the complexity and overhead of an intermediary. Dependency injection frameworks such as Spring and Guice assemble local application components;
- Fabric3 extends assembly from local to distributed services. Fabric3 does not compete with messaging middleware (MOM), but often uses it for remote communication between services.
- Fabric3 does not replace web services but can be used to expose RESTful (JAX-RS) resources and WS-* endpoints to external clients.
- Fabric3 supports polyglot communications including JMS, ZeroMQ and file-based transports. Fabric3 can also be extended to support additional protocols and transports.
Key Concepts
The following sections explain key concepts necessary to understand used when designing, deploying and maintaining distributed applications with Fabric3...
...