SwitchYard is a lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

Wait, what?

You mean like an Enterprise Service Bus (ESB)?  Yeah, kind of.  At it's core, SwitchYard provides an embeddable services runtime with limited dependencies, allowing you to deploy and run services where you need them: inside unit tests, embedded in your own applications, as modules in an OSGi framework, or within an application server.  Of course, there will be modular components on top of core to provide connectivity, transformation, routing and orchestration, and all the other features that are typically associated with an ESB.  The main difference between SwitchYard and traditional ESB offerings is that we are trying to make the runtime a transparent detail in the service lifecycle.  SwitchYard aims to keep you focused on your services by providing tooling to help define, test, and manage the important details of a service - it's contract, policies, configuration, composition, and management .  After all, the least important detail of your service is where it runs.

Features

Here's a brief list of some of the features SwitchYard has to offer. 

Bean Services via CDI

SwitchYard leverages the power of Java EE6 and CDI to allow Java objects to become services by simply adding an @Service annotation to your bean. Your beans are automatically registered at runtime and references to other services can be injected as CDI beans using @Inject. Use CDI in your JSP and JSF applications to inject enterprise services into the web tier. Service composition has never been easier!

Integrated Workflow

Leverage the power of jBPM 5 and BPMN 2 for graphical business process definition and human workflow integration. Contract-based invocation of SwitchYard services keeps your business process free of implementation and binding details.

Declarative Transformation

It’s time to stop using procedural approaches to the ubiquitous problem of data transformation in integration and SOA projects. With declarative transformation in SwitchYard, you define the transformation and the types to which it applies - SwitchYard automatically registers and executes the transformation. Chose from Smooks, Java, XSLT, JSON, and more.

Decision Services with Drools

Encapsulate business rules as decision services using the Drools component in SwitchYard. Each service has a well defined contract with protocol binding details and marshalling details abstracted away by SwitchYard.

Integration with Apache Camel

Define service pipelines using the flexible, EIP-based routing engine from the Apache Camel integration framework. You can also take advantage of the wide variety of Camel components as gateway bindings for SwitchYard services.

Development Made Easy

SwitchYard provides a set of Forge plugins to aid in the rapid development of Maven- based applications. Get further, quicker by using Forge to create and configure your application right out of the gate.

Testing Made Easy

Don't wait until the end of your development cycle to test service-oriented applications as a black box. SwitchYard provides comprehensive unit test support to allow you to test services as you develop them.

Flexible Deployment Options

Take SwitchYard anywhere - integrated with JBoss AS6 and AS7, embedded in your webapp, or loaded from a unit test.

What Problems Are We Trying To Solve?

Developers face two significant challenges when looking to adopt a runtime for a SOA project, whether it's an ESB, an EAI/B2B gateway, MOM, or another flavor of integration middleware.

1) You pay too much.  In other words, the cost of adopting a new SOA runtime and development framework.  This can be measured by the time it takes to get started, the technologies that you're forced to adopt or abandon to play nice with the platform, the bulk of a monolithic runtime and its dependencies, and anything else that consumes your valuable time and resources.

2) You don't get enough in return.  Your deployed applications fall considerably short of the promise of SOA.  Services are tightly coupled, dependencies are unclear, runtime and design-time governance are an afterthought, monitoring is limited and inflexible, clustering is unreliable and a pain to setup.  Worst of all, you end up writing lots of your own code to make it all work.